@waku/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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with consistent publish history; lack of provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@waku/core | AI (dependencies): First-party @waku monorepo package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@waku/proto | AI (dependencies): First-party @waku monorepo package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@waku/utils | AI (dependencies): First-party @waku monorepo package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@waku/sds | AI (dependencies): First-party @waku monorepo package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@waku/interfaces | AI (dependencies): First-party @waku monorepo package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): @noble/hashes is a legitimate declared dep used transitively; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/lodash.debounce | AI (phantom-deps): Type-only package for lodash.debounce which is a direct dep; stable false positive. | ai | |
| dependencies | unvetted-dep:@waku/discovery | AI (dependencies): First-party @waku monorepo package; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.36 | 16 / 16 | |
| 0.0.35 | 16 / 16 | |
| 0.0.32 | 13 / 15 | |
| 0.0.31 | 14 / 15 | |
| 0.0.30 | 14 / 15 | |
| 0.0.29 | 15 / 14 | |
| 0.0.28 | 14 / 9 |
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.