Orgpackage

Orgpackage is a packaging construct used in software development to group, publish, and consume software assets that are owned by a specific organization or business unit. It functions as a namespace within a package registry, enabling organization-scoped identifiers and governance of dependencies across projects.

A typical orgpackage is described by a manifest file that lists its metadata and dependencies. Common fields include name, organization, version, description, license, authors, and a dependency graph. The organization field allows administrators to apply access controls and retention policies at the package level, while versioning supports semantic versioning and compatibility constraints.

Publishing and consumption usually follow a workflow where teams publish orgpackages to a registry and internal tooling installs them via the package manager using the organization prefix or namespace. This enables standardization across projects, supports internal reuse, and facilitates auditing and approval processes.

Naming and scope are central to orgpackage design. Packages are typically referenced with a hierarchical or prefixed name such as orgname/pkg or @orgname/pkg, depending on the ecosystem. This scoping helps prevent naming collisions and clarifies ownership. While most ecosystems support orgscoped packages, the exact syntax varies.

Benefits include improved reuse, policy enforcement, and clearer dependency boundaries. Drawbacks include maintenance overhead, registry fragmentation, and potential onboarding friction for external contributors.

See also namespaces, registries, dependency management and monorepos.