feat: add Cloudsmith registry to benchmarks#68
Merged
darcyclarke merged 1 commit intovltpkg:mainfrom Mar 11, 2026
Merged
Conversation
Add Cloudsmith (npm.cloudsmith.io) as a fourth registry in the
benchmark suite alongside npm, vlt, and AWS CodeArtifact.
Backend:
- Add Cloudsmith registry config to scripts/registry/common.sh
- CLOUDSMITH_REGISTRY env var provides the URL (without protocol)
- CLOUDSMITH_AUTH_TOKEN env var provides the auth token
- Registry URL is prefixed with 'https:' for npm config
- Add Cloudsmith to hyperfine commands in registry-clean.sh and
registry-lockfile.sh
- Add Cloudsmith to REGISTRY_COLORS in generate-chart.js (#2a6fe1)
- Add CLOUDSMITH_REGISTRY and CLOUDSMITH_AUTH_TOKEN secrets to CI
- Update bench CLI: AVAILABLE_REGISTRIES, usage text, examples
Frontend:
- Add 'cloudsmith' to PackageManager union type and all data interfaces
- Add Cloudsmith icon component (diamond + circle from official logo)
- Add Cloudsmith to icon map, display names ('Cloudsmith' / 'npm.cloudsmith.io')
- Add to history data package managers list
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Cloudsmith as a fourth registry in the benchmark suite alongside npm, vlt, and AWS CodeArtifact.
Backend
scripts/registry/common.sh— Cloudsmith registry config usingCLOUDSMITH_REGISTRY(URL without protocol prefix,https:is prepended) andCLOUDSMITH_AUTH_TOKENenv vars for .npmrc auth setupregistry-clean.sh/registry-lockfile.sh— Cloudsmith added to hyperfine commandsgenerate-chart.js— Cloudsmith color:#2a6fe1benchCLI — added to available registries, usage docs, examplesCLOUDSMITH_REGISTRYandCLOUDSMITH_AUTH_TOKENsecrets passed to benchmark jobFrontend
cloudsmithadded toPackageManagertype and all data interfacesCloudsmith/npm.cloudsmith.ioin registry view)Required Secrets
Two GitHub repository secrets need to be configured:
CLOUDSMITH_REGISTRY— the registry URL without protocol (e.g.//npm.cloudsmith.io/org/repo/)CLOUDSMITH_AUTH_TOKEN— the authentication token