@walletconnect/keyvaluestorage
Isomorphic Key-Value Storage
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.es.js | AI (source-diff): Rollup-minified ES build output with readable matching imports; not obfuscation. | ai | |
| phantom-deps | phantom-dep:idb-keyval | AI (phantom-deps): idb-keyval is imported in the minified dist; scanner misses bundled import text. | ai | |
| provenance | no-provenance | AI (provenance): WalletConnect ecosystem package with legitimate publisher; lack of provenance is common and not a risk signal for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 3 / 12 | |
| 1.1.0 | 3 / 13 | |
| 1.0.2 | 2 / 16 | |
| 1.0.0 | 2 / 13 |
v1.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gancho_walletconnect) than the most recent previously approved version (bkrem) on 2023-11-10, but gancho_walletconnect is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bkrem) than the most recent previously approved version (pedrouid) on 2022-11-25, but bkrem is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.