@aztec/p2p
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:@nethermindeth/discv5 | AI (dependencies): Known Nethermind discv5 library used consistently across Aztec p2p versions. | ai | |
| dependencies | unvetted-dep:@nethermindeth/enr | AI (dependencies): Known Nethermind ENR library used consistently across Aztec p2p versions. | ai | |
| dependencies | unvetted-dep:@aztec/noir-protocol-circuits-types | AI (dependencies): Same-org Aztec monorepo package; versioned in lockstep with this package. | ai | |
| phantom-deps | phantom-dep:@aztec/noir-contracts.js | AI (phantom-deps): Same-org Aztec monorepo dep; phantom detection is a false positive for this package structure. | ai | |
| phantom-deps | phantom-dep:@libp2p/prometheus-metrics | AI (phantom-deps): Declared dependency used transitively in libp2p metrics configuration; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:sha3 | AI (phantom-deps): sha3 is a declared dependency used in the P2P/ENR stack; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit TypeScript runtime dependency; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is declared as a dependency and used transitively in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@libp2p/peer-store | AI (phantom-deps): Declared dependency used transitively in libp2p configuration; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @aztec/p2p is a scoped package for Aztec's P2P networking layer; edit-distance match to 'pg' is a false positive with no impersonation intent. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used to deserialize a libp2p peer private key — standard cryptographic key handling for P2P identity, not payload obfuscation. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env spread is in testbench worker spawning code to pass parent environment to child processes — standard practice, not credential exfiltration. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @aztec/p2p is a scoped package for Aztec's P2P networking layer; edit-distance match to 'yup' is a false positive with no impersonation intent. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 35 / 15 | |
| 4.2.1 | 35 / 15 | |
| 4.2.0 | 35 / 15 | |
| 4.1.3 | 35 / 15 | |
| 4.1.2 | 35 / 15 | |
| 4.1.1 | 35 / 15 | |
| 4.1.0 | 35 / 15 | |
| 4.0.3 | 35 / 15 | |
| 4.0.1 | 35 / 15 | |
| 3.0.3 | 35 / 15 | |
| 3.0.2 | 35 / 15 | |
| 3.0.1 | 35 / 15 | |
| 2.1.9 | 35 / 14 | |
| 2.1.8 | 35 / 14 | |
| 2.1.5 | 35 / 14 | |
| 2.1.2 | 35 / 14 | |
| 2.0.4 | 36 / 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
3 findingsSpreading entire process.env into an object — may capture all secrets 75 | execArgv.push('--loader', 'ts-node/esm'); 76 | } > 77 | const env = { 78 | ...process.env, 79 | TS_NODE_PROJECT: tsconfigPath
Spreading entire process.env into an object — may capture all secrets 123 | } 124 | > 125 | const env = { 126 | ...process.env, 127 | TS_NODE_PROJECT: tsconfigPath,
Package 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.1
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.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.