← Home

@coral-xyz/anchor-errors

npm

Anchor error codes

5
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

armaniferrantesolana-devs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Handoff to established Anchor maintainer armaniferrante; stable across versions. ai

Versions (showing 5 of 5)

Version Deps Published
0.32.1 0 / 1
0.32.0 0 / 1
0.31.1 0 / 1
0.31.0 0 / 1
0.30.1 0 / 1

v0.31.1

2 findings
HIGH Publisher changed: acheroncrypto → armaniferrante (on 2025-04-20) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.0

2 findings
HIGH Publisher changed: acheroncrypto → armaniferrante (on 2025-03-09) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.1

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.