@cityofzion/bs-solana
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:bip39 | AI (phantom-deps): bip39 is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai | |
| phantom-deps | phantom-dep:micro-key-producer | AI (phantom-deps): micro-key-producer is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai | |
| dependencies | unvetted-dep:@bonfida/spl-name-service | AI (dependencies): Known Solana name service library; expected dependency for a Solana blockchain service package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-scoped library package; missing description is cosmetic, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present to elevate this. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.1.15 | 9 / 6 | |
| 3.1.14 | 9 / 6 | |
| 3.1.13 | 9 / 6 | |
| 3.1.12 | 9 / 6 | |
| 3.1.11 | 9 / 6 | |
| 3.1.10 | 8 / 6 | |
| 3.1.9 | 8 / 6 | |
| 3.1.8 | 8 / 6 | |
| 3.1.7 | 8 / 6 | |
| 3.1.6 | 8 / 6 | |
| 3.1.5 | 8 / 6 | |
| 3.1.4 | 8 / 6 | |
| 3.1.3 | 8 / 6 | |
| 3.1.2 | 8 / 6 | |
| 3.1.1 | 8 / 6 | |
| 3.1.0 | 8 / 6 | |
| 3.0.6 | 8 / 6 | |
| 3.0.5 | 8 / 6 | |
| 3.0.4 | 12 / 7 | |
| 3.0.3 | 12 / 7 | |
| 3.0.2 | 12 / 7 | |
| 3.0.1 | 12 / 7 | |
| 3.0.0 | 12 / 7 | |
| 2.0.11 | 12 / 7 | |
| 2.0.10 | 12 / 7 | |
| 2.0.9 | 12 / 7 | |
| 2.0.8 | 12 / 7 | |
| 2.0.7 | 12 / 7 |
v3.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.