← Home

@aztec/accounts

npm Homepage
25
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

zac-williamsonleilawangcharlielyejaosefjoss-aztecprotocolludamad

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard implicit dependency from TypeScript transpilation; stable for this package. ai
phantom-deps phantom-dep:@aztec/ethereum AI (phantom-deps): Same-org transitive dependency; expected pattern in Aztec Protocol monorepo. ai
dependencies unvetted-dep:@aztec/aztec.js AI (dependencies): First-party @aztec monorepo dependency at matching version; not a third-party risk. ai
dependencies unvetted-dep:@aztec/ethereum AI (dependencies): First-party @aztec monorepo dependency at matching version; not a third-party risk. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decode is used for ECDSA low-S normalization (BigInt to Buffer conversion) — standard cryptographic pattern, not a malicious payload. ai
dependencies unvetted-dep:@aztec/entrypoints AI (dependencies): First-party @aztec monorepo dependency at matching version; not a third-party risk. ai
dependencies unvetted-dep:@aztec/foundation AI (dependencies): First-party @aztec monorepo dependency at matching version; not a third-party risk. ai
dependencies unvetted-dep:@aztec/stdlib AI (dependencies): First-party @aztec monorepo dependency at matching version; not a third-party risk. ai

Versions (showing 25 of 25)

Version Deps Published
4.3.1 6 / 9
4.3.0 6 / 9
4.2.1 6 / 9
4.2.0 6 / 9
4.1.3 6 / 9
4.1.2 6 / 9
4.1.1 6 / 9
4.1.0 6 / 9
4.0.4 6 / 9
4.0.3 6 / 9
4.0.2 6 / 9
4.0.1 6 / 9
3.0.3 6 / 9
3.0.2 6 / 9
3.0.1 6 / 9
2.1.11 6 / 8
2.1.9 6 / 8
2.1.8 6 / 8
2.1.7 6 / 8
2.1.6 6 / 8
2.1.5 6 / 8
2.1.4 6 / 8
2.1.3 6 / 8
2.1.2 6 / 8
2.0.4 6 / 8

v4.3.1

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

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

v4.1.3

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.

v4.1.2

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.

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.4

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

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.

v2.1.2

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.

v2.0.4

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.