@coral-xyz/anchor
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:crypto-hash | AI (phantom-deps): Legit small hashing dep in a well-known package; likely used in compiled output not scanned. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate handoff to Anchor founder armaniferrante; established high-trust package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Solana framework package; sparse README is typical for scoped SDK sub-packages. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.32.1 | 13 / 28 | |
| 0.32.0 | 13 / 28 | |
| 0.31.1 | 13 / 28 | |
| 0.31.0 | 13 / 28 | |
| 0.30.1 | 15 / 28 | |
| 0.30.0 | 14 / 28 | |
| 0.29.0 | 14 / 28 | |
| 0.28.0 | 15 / 28 | |
| 0.27.0 | 15 / 28 | |
| 0.26.0 | 15 / 28 |
v0.31.1
2 findingsThis version was published by a different npm account than previous versions on 2025-04-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
2 findingsThis version was published by a different npm account than previous versions on 2025-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.