← Home

@aztec/blob-client

npm
12
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

zac-williamsonleilawangcharlielyejaosefjoss-aztecprotocolludamad

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit dependency of TypeScript; stable for this package. ai
phantom-deps phantom-dep:express AI (phantom-deps): express is referenced in jest config; legitimate config-level dependency. ai
phantom-deps phantom-dep:@aztec/kv-store AI (phantom-deps): Same-org scoped dependency; likely implicitly required by other @aztec packages in monorepo. ai
phantom-deps phantom-dep:source-map-support AI (phantom-deps): source-map-support is referenced in jest setup config; legitimate config-level dependency. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding in parseBlobJson is standard EIP-4844 blob/KZG commitment parsing from API responses. No obfuscation or malicious payload construction present; stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
4.3.1 12 / 11
4.3.0 12 / 11
4.2.1 12 / 11
4.2.0 12 / 11
4.1.3 12 / 11
4.1.2 12 / 11
4.1.1 12 / 11
4.1.0 12 / 11
4.0.4 12 / 11
4.0.3 12 / 11
4.0.2 12 / 11
4.0.1 12 / 11

v4.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.0

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.

v4.1.3

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.

v4.1.2

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.

v4.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

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.

v4.0.2

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.

v4.0.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.