FAQ-001418 - Package Version Visibility and Scanner Access Issues / Package Version Selection and Dropdown Issues

If you're experiencing issues with package version selection or empty dropdowns in security scanning tools, follow these steps to resolve them: 1. **Ensure Package Status:** The package must be either managed-beta or managed-released. For second-generation packages (2GP), the version must be promoted to "Released." 2. **Use Correct Organization:** Use the same Dev Hub or Developer Edition org that was used to create the package. 3. **Check Version Limit:** Confirm that the version is among the last 10 versions of the package, as only the most recent 10 are displayed in the portal. 4. **Verify Partner Community Connection:** Ensure that the package version is visible in the Partner Community under Publishing → Technologies → Partner Security Portal Solutions tab. If the issue persists after checking these points, you may need to raise a support case for further assistance.

After reviewing this FAQ, I found no issues that require changes or rule associations. This FAQ addresses purely operational/portal access issues related to package visibility in security scanning tools, not security vulnerabilities or code security practices. The content covers: 1. Package status requirements (managed-beta/managed-released, 2GP promotion) 2. Organizational setup (Dev Hub/Developer Edition org usage) 3. Version limitations (10-version display limit) 4. Partner Community visibility verification These are all administrative/portal configuration issues, not security code analysis concerns. None of the available security rules (which focus on code security issues like ApexBadCrypto, ApexCRUDViolation, XSS prevention, etc.) apply to package visibility or dropdown population problems. The existing answer is clear, well-structured, and provides actionable troubleshooting steps. The tone is appropriate and follows the guidelines for being direct and helpful. No technical content appears outdated or inaccurate. No rule associations were made because this FAQ is about portal/infrastructure issues rather than security code practices that the scanner rules are designed to detect.