Protected packages: "Protected" badge not visible in group level view
Problem Statement
Currently, the "Protected" badge for protected packages is not visible when viewing packages at the group level. This lack of visual indication makes it difficult for users to quickly identify which packages are protected within a group.
This bug issue is similar to the big issue described #506539 (closed) in the context of protected containers.
Expected Behavior
When viewing packages at the group level, protected packages should include a "Protected" badge, similar to how they are displayed at the project level.
Current Behavior
The "Protected" badge is missing when viewing packages in the group level view, even though the packages are actually protected.
Steps to Reproduce
- Navigate to a group that contains projects with protected packages
- Go to the "Deploy" => "Package Registry"
- View the list of packages
- Observe that some protected packages do not include a "Protected" badge
Impact
This issue affects users' ability to quickly identify protected packages at the group level, which can lead to confusion and potential security risks if users are not aware of a package's protected status.
Proposed Solution
Implement the display of the "Protected" badge for protected packages when viewing them at the group level, ensuring consistency with the project-level view.
Additional Information
- This issue only affects the group-level view; the "Protected" badge is correctly displayed at the project level.
- The backend correctly identifies protected packages; this appears to be a frontend display issue.