@zoralabs/protocol-sdk
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established SDK package; sparse README/keywords are a style choice, not spam indicators. | ai | |
| dependencies | unvetted-dep:@zoralabs/protocol-deployments | AI (dependencies): Same-org sibling package; stable dependency relationship across many versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.13.21 | 1 / 15 | |
| 0.13.18 | 1 / 15 | |
| 0.13.16 | 1 / 15 | |
| 0.13.15 | 1 / 15 | |
| 0.13.11 | 1 / 15 | |
| 0.13.9 | 1 / 15 | |
| 0.13.8 | 1 / 15 | |
| 0.13.7 | 1 / 15 |
v0.13.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.