@coral-xyz/borsh
Anchor Borsh
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Stale publisher change, long-established package, no malicious diff. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with legitimate org handoff, not takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Change is 1138d old and unremoved, inconsistent with compromise. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Legitimate @coral-xyz scoped package; not a typosquat of cors — different ecosystem and purpose entirely. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.32.1 | 2 / 1 | |
| 0.32.0 | 2 / 1 | |
| 0.31.1 | 2 / 1 | |
| 0.31.0 | 2 / 1 | |
| 0.30.1 | 2 / 1 | |
| 0.30.0 | 2 / 1 | |
| 0.29.0 | 2 / 1 | |
| 0.28.0 | 2 / 1 | |
| 0.27.0 | 2 / 1 | |
| 0.26.0 | 2 / 1 | |
| 0.2.6 | 2 / 0 |
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
2 findingsThis version was published by a different npm account (acheroncrypto) than the most recent previously approved version (henrye) on 2024-04-15. It has since remained available on npm for 827 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
2 findingsThis version was published by a different npm account (acheroncrypto) than the most recent previously approved version (henrye) on 2023-10-16. It has since remained available on npm for 1009 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
2 findingsThis version was published by a different npm account (acheroncrypto) than the most recent previously approved version (henrye) on 2023-06-09. It has since remained available on npm for 1138 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.