@walletconnect/modal
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/cdn/index-44322b32.js | AI (source-diff): Standard rollup/lit CDN bundle, not true obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Rename from @web3modal/* to official @walletconnect/modal-* namespace. | ai | |
| source-diff | obfuscated-file:dist/cdn/index-082b7b20.js | AI (source-diff): Bundled Lit/rollup CDN output, not true obfuscation; expected for unpkg build target. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is the new CDN bundle file, consistent with build output. | ai | |
| provenance | no-provenance | AI (provenance): WalletConnect packages consistently lack Sigstore provenance; not a risk signal for this publisher. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.7.0 | 2 / 0 | |
| 2.5.7 | 2 / 0 | |
| 2.5.4 | 2 / 0 | |
| 2.4.6 | 2 / 0 | |
| 2.4.5 | 2 / 0 | |
| 2.4.4 | 2 / 0 | |
| 2.4.3 | 2 / 0 |
v2.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
2 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.
v2.4.6
2 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.
v2.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.