@waku/sdk
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
royerfranckweboko
Keywords
wakudecentralizedsecurecommunicationweb3ethereumdappsprivacy
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 |
v0.0.35
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.
v0.0.32
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.