← Home

@openzeppelin/defender-sdk-deploy-client

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): OpenZeppelin is a well-established organization; lack of Sigstore provenance is common and not indicative of risk for this package. ai
dependencies unvetted-dep:@openzeppelin/defender-sdk-base-client AI (dependencies): Sibling package in the same OpenZeppelin Defender SDK monorepo; dependency is expected and benign. ai

Versions (showing 3 of 3)

Version Deps Published
2.7.1 3 / 0
2.7.0 3 / 0
2.6.0 3 / 0

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.