Package ownership and visibility
How project visibility and team ownership affect published artifacts.
Concepts
A GitMyABI project belongs to a user or a team and carries a visibility setting that influences how its build artifacts can be discovered and consumed.
Package ownership and visibility rules depend on workspace, project, and registry behaviour. Until this page is complete, use the publishing guide and the billing page for confirmed behaviour, and treat the values shown on each build detail page as authoritative.
- Projects FAQ — project basics, including private and organisation repositories.
- Publish generated contract bindings to npm — per-project publishing setup.
- Billing and subscriptions — plan-gated visibility and team features.
Related
- Contract ABI
What a smart contract ABI is and why it matters.
- Generated contract bindings
TypeScript packages produced from contract ABIs for typed integration.
- ABI and bindings publishing
How GitMyABI delivers ABIs via CDN and bindings via npm.
- Projects and builds
How a GitMyABI project maps to a GitHub repository and how builds produce artifacts.