@walletconnect/utils
Utilities 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Standard Rollup bundle output; not obfuscated. Stable for this package. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Standard Rollup bundle output; not obfuscated. Stable for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ox is a vetted Ethereum primitives lib replacing viem; not a suspicious addition for this package. | ai | |
| phantom-deps | phantom-dep:@noble/ciphers | AI (phantom-deps): @noble/ciphers is a reputable cryptography library; phantom finding reflects monorepo bundler config usage, not a real risk for this package. | ai | |
| phantom-deps | phantom-dep:@walletconnect/safe-json | AI (phantom-deps): Same-org WalletConnect package; phantom finding reflects monorepo bundler config usage, not a real risk. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): @noble/curves is a reputable cryptography library; phantom finding reflects monorepo bundler config usage, not a real risk for this package. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): @noble/hashes is a reputable cryptography library; phantom finding reflects monorepo bundler config usage, not a real risk for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): WalletConnect rebranded to Reown; new publisher account but same canonical monorepo with SLSA provenance. Inflated semver is continuation of existing version line. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 2.23.9 | 19 / 2 | |
| 2.23.8 | 19 / 2 | |
| 2.23.7 | 19 / 2 | |
| 2.23.6 | 19 / 2 | |
| 2.23.5 | 19 / 2 | |
| 2.23.4 | 20 / 2 | |
| 2.23.3 | 20 / 2 | |
| 2.23.2 | 20 / 2 | |
| 2.23.1 | 20 / 2 | |
| 2.23.0 | 20 / 2 | |
| 2.22.4 | 20 / 2 | |
| 2.22.3 | 20 / 2 | |
| 2.22.2 | 20 / 2 | |
| 2.22.1 | 19 / 2 | |
| 2.22.0 | 19 / 2 | |
| 2.21.10 | 19 / 2 | |
| 2.21.9 | 19 / 2 | |
| 2.21.8 | 20 / 2 | |
| 2.21.7 | 20 / 2 | |
| 2.21.6 | 20 / 2 | |
| 2.21.5 | 20 / 2 | |
| 2.21.4 | 20 / 2 | |
| 2.21.3 | 20 / 2 | |
| 2.21.2 | 20 / 2 | |
| 2.21.1 | 17 / 2 | |
| 2.21.0 | 17 / 2 | |
| 2.20.3 | 17 / 2 | |
| 2.20.2 | 17 / 2 | |
| 2.20.1 | 17 / 2 |
v2.23.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.22.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.