@waku/sds
Scalable Data Sync implementation for the browser. Based on https://github.com/vacp2p/rfc-index/blob/main/vac/raw/sds.md
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @waku/sds package; Levenshtein match to 'qs' is a spurious artifact of the short suffix, not a typosquat. | ai | |
| phantom-deps | phantom-dep:chai | AI (phantom-deps): chai is listed as a runtime dep (likely accidentally) but not imported; no security risk. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.0.8 | 6 / 11 | |
| 0.0.7 | 6 / 11 | |
| 0.0.6 | 6 / 11 | |
| 0.0.5 | 5 / 11 | |
| 0.0.4 | 5 / 11 | |
| 0.0.3 | 6 / 11 | |
| 0.0.2 | 5 / 11 | |
| 0.0.1 | 5 / 11 |
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.