@rainbow-me/rainbowkit
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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/magicEden-PKT2ZXEQ.js | AI (source-diff): Inline SVG path data for wallet icon, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/wallets/walletConnectors/magicEden-PKT2ZXEQ.js | AI (source-diff): Duplicate of above — bundled SVG wallet icon asset. | ai | |
| phantom-deps | phantom-dep:@vanilla-extract/css | AI (phantom-deps): Build-time CSS-in-JS tool referenced in config; not a runtime import, stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.2.11 | 7 / 14 | |
| 2.2.10 | 7 / 15 | |
| 2.2.6 | 7 / 15 | |
| 2.2.5 | 7 / 15 | |
| 2.1.2 | 7 / 14 | |
| 2.1.1 | 7 / 14 | |
| 2.1.0 | 7 / 13 | |
| 2.0.8 | 8 / 13 | |
| 2.0.7 | 8 / 13 |
v2.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
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
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.