@aztec/prover-node
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @aztec/native from the same org at the same version — routine monorepo release, not an external injection. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance absence is common in org-scoped packages. | ai | |
| dependencies | unvetted-dep:@aztec/node-lib | AI (dependencies): Same-org @aztec scoped dependency pinned to matching version in a coordinated monorepo release; not an independent third-party risk. | ai | |
| dependencies | unvetted-dep:@aztec/noir-protocol-circuits-types | AI (dependencies): Same-org @aztec scoped dependency pinned to matching version in a coordinated monorepo release; not an independent third-party risk. | ai | |
| phantom-deps | phantom-dep:@aztec/protocol-contracts | AI (phantom-deps): Same @aztec org scope; phantom dep pattern is expected in TypeScript monorepo with type-only or transitive imports across sibling packages. | ai | |
| phantom-deps | phantom-dep:@aztec/noir-protocol-circuits-types | AI (phantom-deps): Same @aztec org scope; phantom dep pattern is expected in TypeScript monorepo with type-only or transitive imports across sibling packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @aztec/* monorepo packages; not a spam/malware indicator for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@aztec/p2p | AI (phantom-deps): Same-org scoped package; declared as dependency for transitive/runtime use, not direct import. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is referenced in config files rather than direct imports; legitimate pattern. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard TypeScript runtime helper; declared but not directly imported is expected behavior. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata (no README code, no keywords, no repo URL) is typical for @aztec/* scoped packages published as part of a coordinated release. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 25 / 9 | |
| 4.2.0 | 25 / 9 | |
| 4.1.3 | 25 / 9 | |
| 4.1.2 | 25 / 9 | |
| 4.1.0 | 25 / 9 | |
| 4.0.4 | 24 / 9 | |
| 4.0.3 | 24 / 9 | |
| 4.0.2 | 24 / 9 | |
| 4.0.1 | 24 / 9 | |
| 2.1.9 | 24 / 8 | |
| 2.1.7 | 24 / 8 | |
| 2.1.6 | 24 / 8 | |
| 2.1.3 | 24 / 8 | |
| 2.1.2 | 24 / 8 | |
| 2.0.4 | 24 / 8 |
v4.2.1
1 finding[Accepted risk] Package 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.