@aztec/bb-prover
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aztec/noir-protocol-circuits-types | AI (dependencies): Sibling package within the same @aztec monorepo, always released at matching versions. Not an external unvetted dependency. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; description omitted by convention. Stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is part of the @aztec monorepo with 962 versions and 10 approved dependents; missing metadata fields are a monorepo convention, not spam indicators. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): ZK circuit bytecodes are routinely base64-encoded binary data; Buffer.from(bytecode, 'base64') is standard and expected in a ZK prover package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is explicitly listed as a runtime dependency in package.json and is a standard TypeScript runtime helper; not a phantom dependency. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 14 / 15 | |
| 4.2.1 | 14 / 15 | |
| 4.2.0 | 14 / 15 | |
| 4.1.3 | 14 / 15 | |
| 4.1.2 | 14 / 15 | |
| 4.1.1 | 14 / 15 | |
| 4.1.0 | 14 / 15 | |
| 4.0.4 | 14 / 15 | |
| 4.0.3 | 14 / 15 | |
| 4.0.2 | 14 / 15 | |
| 3.0.3 | 14 / 15 | |
| 3.0.2 | 14 / 15 | |
| 3.0.1 | 14 / 15 | |
| 2.1.9 | 14 / 14 | |
| 2.1.8 | 14 / 14 | |
| 2.1.6 | 14 / 14 | |
| 2.1.4 | 14 / 14 | |
| 2.1.3 | 14 / 14 | |
| 2.1.2 | 14 / 14 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.