@aztec/prover-client
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): Same-org @aztec/* dependency following identical versioning pattern as all other deps in this monorepo package. Not a genuine risk. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Used in compiled CLI entry points (bb script); phantom-dep analyzer may not trace through compiled output. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): Loaded via config/setup files rather than direct import; standard pattern for source map support in Node.js packages. | ai | |
| phantom-deps | phantom-dep:@iarna/toml | AI (phantom-deps): Referenced in config files per analyzer note; legitimate dependency for TOML parsing in the Aztec toolchain. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declared as dependency for downstream consumers, not always directly imported in source. | ai | |
| phantom-deps | phantom-dep:@aztec/noir-types | AI (phantom-deps): Same-org sibling package; phantom detection in monorepo context is expected when imports are re-exported through other @aztec packages. | ai | |
| phantom-deps | phantom-dep:lodash.chunk | AI (phantom-deps): Referenced in config files per analyzer note; legitimate utility dependency. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @aztec monorepo publishing pattern; not indicative of malicious intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing README/description/repo URL is standard for programmatically published @aztec packages, not a spam indicator. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 19 / 11 | |
| 4.2.0 | 19 / 11 | |
| 4.1.3 | 19 / 11 | |
| 4.1.2 | 19 / 11 | |
| 4.1.1 | 19 / 11 | |
| 3.0.1 | 20 / 11 | |
| 2.1.11 | 20 / 10 | |
| 2.1.8 | 20 / 10 | |
| 2.1.7 | 20 / 10 | |
| 2.1.3 | 20 / 10 | |
| 2.1.2 | 20 / 10 | |
| 2.0.4 | 20 / 10 |
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.
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.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.