@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 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 10.0.1 | 23 / 17 | |
| 10.0.0 | 23 / 17 | |
| 9.1.4 | 23 / 17 | |
| 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 | |
| 7.1.6 | 23 / 16 | |
| 7.1.5 | 23 / 16 | |
| 7.1.4 | 23 / 16 | |
| 7.1.3 | 23 / 16 | |
| 7.1.2 | 23 / 16 | |
| 7.1.1 | 23 / 16 | |
| 7.1.0 | 23 / 16 | |
| 7.0.11 | 23 / 16 | |
| 7.0.10 | 23 / 16 | |
| 7.0.9 | 23 / 16 | |
| 7.0.8 | 23 / 16 | |
| 7.0.7 | 23 / 16 | |
| 7.0.6 | 23 / 16 | |
| 7.0.5 | 23 / 16 | |
| 7.0.4 | 23 / 16 | |
| 7.0.3 | 23 / 16 | |
| 7.0.2 | 23 / 16 | |
| 7.0.1 | 23 / 16 | |
| 7.0.0 | 23 / 16 | |
| 6.1.1 | 23 / 16 | |
| 6.1.0 | 23 / 16 | |
| 6.0.10 | 23 / 16 | |
| 6.0.9 | 25 / 14 | |
| 6.0.8 | 25 / 14 | |
| 6.0.7 | 25 / 14 | |
| 6.0.6 | 25 / 14 | |
| 6.0.5 | 25 / 14 | |
| 6.0.4 | 25 / 14 | |
| 6.0.3 | 25 / 14 | |
| 6.0.2 | 25 / 14 | |
| 6.0.1 | 25 / 14 | |
| 6.0.0 | 25 / 14 | |
| 5.1.2 | 25 / 14 |
v10.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (pedromcunha-uneven) on 2026-07-21, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v9.1.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (pedromcunha-uneven) on 2026-07-10, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v7.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.