@walletconnect/sign-client
Sign Client for WalletConnect Protocol
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@walletconnect/jsonrpc-provider | AI (phantom-deps): Same-org dep, likely used via bundled build output. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): Used as pino transport at runtime, not statically imported. | ai | |
| provenance | publisher-changed | AI (provenance): Known WalletConnect→Reown org transition; publisher has strong approved track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old WalletConnect maintainer dropped as part of Reown rebrand. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same documented org transition to reown-npm-org. | ai | |
| source-diff | encoded-string-file:dist/index.umd.js | AI (source-diff): Rollup UMD build output; long strings are bundled minified code, not obfuscated payload. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Rollup-bundled ESM output; standard minification for this package. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Rollup-bundled CJS output; standard minification for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and short README are expected for a monorepo sub-package migrating to a new npm org scope; version tracks monorepo release cadence. Not indicative of spam or malicious intent. | ai | |
| phantom-deps | phantom-dep:@walletconnect/heartbeat | AI (phantom-deps): Same-org dependency declared for transitive use via @walletconnect/core; not a phantom dep concern for this package. | ai | |
| phantom-deps | phantom-dep:@walletconnect/events | AI (phantom-deps): Same-org dependency declared for transitive use via @walletconnect/core; not a phantom dep concern for this package. | ai |
Versions (showing 20 of 120)
| Version | Deps | Published |
|---|---|---|
| 2.4.6 | 11 / 4 | |
| 2.4.5 | 11 / 4 | |
| 2.4.4 | 11 / 4 | |
| 2.4.3 | 11 / 4 | |
| 2.4.2 | 11 / 4 | |
| 2.4.1 | 11 / 4 | |
| 2.4.0 | 11 / 4 | |
| 2.3.3 | 11 / 4 | |
| 2.3.2 | 11 / 4 | |
| 2.3.1 | 11 / 4 | |
| 2.3.0 | 11 / 4 | |
| 2.2.1 | 11 / 4 | |
| 2.2.0 | 11 / 4 | |
| 2.1.5 | 11 / 4 | |
| 2.1.4 | 11 / 4 | |
| 2.1.3 | 10 / 4 | |
| 2.1.2 | 9 / 4 | |
| 2.1.1 | 11 / 4 | |
| 2.1.0 | 11 / 4 | |
| 2.0.0 | 11 / 4 |
v2.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.