@openzeppelin/defender-sdk-network-client
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
frangionamiszeljkoxdylkilmcarlomagnocollins-oztirumerlabjmrqpasevinson-oz
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dependency in package.json; phantom-dep fires because it's not directly imported in source but is used in compiled TypeScript output. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dependency in package.json; phantom-dep fires because it's not directly imported in source but is used in compiled TypeScript output. Stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Short README and missing keywords are typical of monorepo SDK sub-packages. Package has legitimate repo URL, author, and 34 published versions under the OpenZeppelin namespace. | ai |
v2.7.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.