Package Visibility

Control access to your packages with visibility settings.

Visibility Levels

Private (Default)

Only workspace members can access:

curl -X PATCH https://registry.yourcompany.com/v1/packages/pkg_ID \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"visibility": "private"}'

Internal (Enterprise)

Accessible across organization workspaces:

curl -X PATCH https://registry.yourcompany.com/v1/packages/pkg_ID \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"visibility": "internal"}'

Public

Anyone with registry access can view:

curl -X PATCH https://registry.yourcompany.com/v1/packages/pkg_ID \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{"visibility": "public"}'

Access Control

Visibility works with RBAC:

Use Cases

Private - Proprietary code, internal tools Internal - Shared across teams Public - Open source, public utilities

Best Practices

1. Default to private for proprietary code
2. Review before making public
3. Document visibility in README
4. Use internal for cross-team packages

Next Steps

• Deprecation - Deprecate packages
• Security - Security best practices