@aztec/blob-lib
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:c-kzg | AI (dependencies): c-kzg is the official Ethereum KZG cryptography native binding (ethereum/c-kzg-4844); its use in a blob/EIP-4844 library is expected and legitimate. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is declared as a runtime dependency and is a well-known implicit dependency of TypeScript-compiled packages; stable false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in blob-lib is standard Ethereum blob/KZG data handling (stripping 0x prefix). Legitimate cryptographic use, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Missing metadata fields are inherited from monorepo root package.common.json. Package has 442 days history, 909 versions, and 12k weekly downloads — clearly not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Description is inherited from monorepo root config. Package is well-established with significant download history. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 4 / 8 | |
| 4.3.0 | 4 / 8 | |
| 4.2.1 | 4 / 8 | |
| 4.2.0 | 4 / 8 | |
| 4.1.3 | 4 / 8 | |
| 4.1.2 | 4 / 8 | |
| 4.1.1 | 4 / 8 | |
| 4.1.0 | 4 / 8 | |
| 4.0.4 | 4 / 8 | |
| 4.0.3 | 4 / 8 | |
| 4.0.2 | 4 / 8 | |
| 4.0.1 | 4 / 8 | |
| 3.0.3 | 4 / 8 | |
| 3.0.2 | 4 / 8 | |
| 3.0.1 | 4 / 8 | |
| 2.1.9 | 4 / 7 | |
| 2.1.8 | 4 / 7 | |
| 2.1.6 | 4 / 7 | |
| 2.1.5 | 4 / 7 | |
| 2.1.3 | 4 / 7 | |
| 2.0.4 | 4 / 7 |
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
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.