@aztec/stdlib
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:@aztec/bb.js | AI (phantom-deps): Same-org dependency (@aztec scope); phantom detection is a false positive for monorepo-style packages. | ai | |
| dependencies | unvetted-dep:@aztec/bb.js | AI (dependencies): Same-org (@aztec) dependency pinned to matching version in a monorepo release pattern; not a meaningful risk for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in @aztec/stdlib is used for parsing ABI debug symbols (decompressing zlib-compressed data). Standard cryptographic/ZK tooling pattern, not a malicious payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is pervasive in blockchain/ZK stdlib for parsing addresses, selectors, and cryptographic primitives. Expected and legitimate for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 21 / 18 | |
| 4.3.0 | 21 / 18 | |
| 4.2.1 | 21 / 17 | |
| 4.2.0 | 21 / 17 | |
| 4.1.3 | 21 / 17 | |
| 4.1.2 | 21 / 17 | |
| 4.1.1 | 21 / 17 | |
| 4.1.0 | 21 / 17 | |
| 4.0.4 | 21 / 17 | |
| 4.0.3 | 21 / 17 | |
| 4.0.2 | 21 / 17 | |
| 4.0.1 | 21 / 17 | |
| 3.0.3 | 20 / 17 | |
| 3.0.2 | 20 / 17 | |
| 3.0.1 | 20 / 17 | |
| 2.1.11 | 20 / 16 | |
| 2.1.9 | 20 / 16 | |
| 2.1.8 | 20 / 16 | |
| 2.1.7 | 20 / 16 | |
| 2.1.6 | 20 / 16 | |
| 2.1.5 | 20 / 16 | |
| 2.1.4 | 20 / 16 | |
| 2.1.3 | 20 / 16 | |
| 2.1.2 | 20 / 16 | |
| 2.0.4 | 19 / 16 |
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.