@stacks/bns
3
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
ablanksteinblockstack-devopsstacks-foundationjannik-stacksrafa-stacks
Keywords
BNSBlockchainBlockstackNamingStacksSystem
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher with SLSA attestation; consistent with Hiro Systems org-level CI/CD migration. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are stacks-org accounts; consistent with legitimate team transition at Hiro Systems. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of zone117x alongside addition of org accounts consistent with planned maintainer rotation. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @stacks package from Hiro Systems; edit-distance match to 'qs' is a heuristic false positive. | ai |
v7.4.0
2 findings
HIGH
Publisher changed: blockstack-devops → GitHub Actions (on 2026-05-22)
provenance
This version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.