Access policy defines what a visitor can see and download. It also keeps release history separate from active artifact delivery so that old records can remain visible without distributing obsolete packages.
Visibility states
- Public: visible in catalog lists and accessible by direct URL.
- Unlisted: hidden from catalog lists but accessible by direct URL.
- Private: blocked from public pages and feeds.
- Archived: retained for review with downloads and update delivery disabled.
Download rules
A release should be downloadable when it is public-safe, not archived and has a stored release artifact. Stability labels such as alpha, beta or RC should not block download availability by themselves.
404 vs private access
A missing file should be reported as a file problem. A private or blocked object should show a private-access message. Keeping these states separate makes debugging release upload issues much easier.