@relayprotocol/relay-kit-ui
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:@types/react | AI (phantom-deps): Type-only peer dep; not directly imported by convention — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only peer dep; not directly imported by convention — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:pandacss-preset-radix-colors | AI (phantom-deps): Referenced in panda config files, not direct imports — stable false positive for this package. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): eclipse.xyz is the legitimate Eclipse blockchain RPC endpoint; not a C2/exfiltration domain. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): FontAwesome core is a transitive peer of react-fontawesome; phantom-dep heuristic fires but it's a stable false positive. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.0.7 | 23 / 17 | |
| 8.0.6 | 23 / 17 | |
| 8.0.5 | 23 / 17 | |
| 8.0.4 | 23 / 17 | |
| 8.0.3 | 23 / 17 | |
| 8.0.2 | 23 / 17 | |
| 8.0.1 | 23 / 17 | |
| 8.0.0 | 23 / 17 | |
| 5.1.2 | 25 / 14 |
v8.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.