@radix-effects/gateway
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@radix-effects/sbor | AI (phantom-deps): Same org scope as this package; phantom-dep is a stable false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Small ecosystem package; no CI provenance setup is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:@radixdlt/babylon-core-api-sdk | AI (phantom-deps): Newly added runtime dep; referenced in config/type files rather than direct imports — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@radixdlt/radix-engine-toolkit | AI (phantom-deps): Likely used as a type dependency or transitively; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@steleaio/radix-engine-toolkit | AI (phantom-deps): Declared as a dependency and referenced in config; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.6.2 | 8 / 6 | |
| 0.6.0 | 8 / 6 | |
| 0.5.0 | 8 / 6 | |
| 0.4.2 | 8 / 6 | |
| 0.4.1 | 8 / 6 | |
| 0.4.0 | 8 / 6 | |
| 0.3.2 | 7 / 6 | |
| 0.3.1 | 7 / 6 | |
| 0.3.0 | 7 / 6 | |
| 0.2.1 | 7 / 6 | |
| 0.2.0 | 7 / 6 | |
| 0.1.0 | 6 / 6 |
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.