Open Source Ecosystem › Package Registries & Distribution

Package Registries & Distribution

AE-250.10 Level 2 API Evangelist extension API Evangelist extension, CC BY-NC-SA 29 providers 65 API surfaces 10 rated strong or better

Publishing and installing open source packages and images from public registries.

Package Registries & Distribution (AE-250.10) is a level-2 business capability under Open Source Ecosystem in the API Evangelist extension model. The catalog holds 65 API surface(s) from 29 provider(s) that can perform some part of it, 10 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of the API Evangelist extension to the business-capability model, written by API Evangelist and licensed CC BY-NC-SA 4.0. API Evangelist capability extension — https://apievangelist.com Audience: b2b It extends, and never modifies, Turbo EA Capabilities by Vincent Verdet (CC BY 4.0). · Extension provenance and licence

Sub-capabilities

Language Package Registries AE-250.10.10API Evangelist extension, CC BY-NC-SA

b2b

npm, Maven Central, PyPI-style registries.

no catalog coverage

Container Registries AE-250.10.20API Evangelist extension, CC BY-NC-SA

b2b

Public and private registries for container images.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 5 Complete, well-documented, and agent-ready
GitHubPackages1 API74.3CircleCIOrb PackagesOrb Versions2 APIs72.6GiteaPackage1 API69.3Eclipse Foundationregistry-apivs-code-api2 APIs66.8JFrog ArtifactoryArtifacts & StorageManifestsRepositories3 APIs66.6
Strong 5 Solid coverage with minor gaps
Microsoft .NETPackageContentRegistration2 APIs65.5AnacondaArtifactsChannels2 APIs65.0Red Hat Ansible Automation PlatformAnsible: CollectionsApi: Content V3 Collections VersionsApi: Content V3 Plugin Ansible Content Collections ArtifactsApi: V3 Collections21 APIs63.4GoHarborRepository1 API59.6Amazon CodeArtifactamazon-codeartifact-operations-apiamazon-codeartifact-package-group-api2 APIs56.6
Developing 16 Usable, with meaningful gaps to close
Buildpacks IoBuildpacks1 API53.5BallerinaConnectorsPackages2 APIs51.5JetifyPkgResolve2 APIs50.0npmPackages1 API49.7NuGetFlatcontainerRegistration2 APIs47.5PulumiRegistry1 API45.6Google FlutterPackages1 API44.7Docker HubRepositories1 API44.0BazelModules1 API43.8GitLab CI/CDPackages1 API43.8TerraformModules1 API43.4Artifact HubPackagesRepositories2 APIs43.1Ansible RolesCollectionsRoles2 APIs42.7Ruby Programming Language and Popular API GemsGems1 API42.4crates.ioCratesVersions2 APIs40.2QuayManifest1 API39.7
Thin 3 Limited public surface area
TimoniArtifactsModules2 APIs36.5HelmChartMuseumChartsRepository3 APIs35.0UbuntuRefresh1 API34.7
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Package Registries & Distribution. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →