@funkit/fun-relay
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@relayprotocol/relay-svm-wallet-adapter | AI (dependencies): Core dependency of this relay SDK wrapper; expected and consistent across versions. | ai | |
| dependencies | unvetted-dep:@relayprotocol/relay-tron-wallet-adapter | AI (dependencies): Core dependency of this relay SDK wrapper; expected and consistent across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established funkit org package with 68 versions; sparse README is a style choice, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped org package with clear naming convention; missing description is cosmetic. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 4 / 6 | |
| 2.7.4 | 4 / 6 | |
| 2.7.3 | 4 / 6 | |
| 2.7.2 | 4 / 6 | |
| 2.7.1 | 4 / 6 | |
| 2.7.0 | 4 / 6 | |
| 2.6.7 | 4 / 6 | |
| 2.6.6 | 4 / 6 | |
| 2.6.5 | 4 / 6 | |
| 2.6.4 | 4 / 6 | |
| 2.6.3 | 4 / 6 | |
| 2.6.2 | 4 / 6 | |
| 2.6.1 | 4 / 6 | |
| 2.6.0 | 4 / 6 | |
| 2.5.0 | 4 / 6 | |
| 2.4.0 | 4 / 6 | |
| 2.3.0 | 4 / 6 | |
| 2.2.2 | 4 / 6 | |
| 2.2.1 | 4 / 6 | |
| 2.2.0 | 4 / 6 | |
| 2.1.15 | 3 / 5 | |
| 2.1.14 | 3 / 5 | |
| 2.1.13 | 3 / 5 | |
| 2.1.12 | 3 / 5 | |
| 2.1.8 | 3 / 5 | |
| 2.1.6 | 3 / 5 | |
| 2.1.4 | 3 / 5 | |
| 2.0.0 | 3 / 2 |
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.