@unruggable/gateways
Trustless Ethereum Multichain CCIP-Read 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:semantic-release | AI (phantom-deps): Config-referenced release automation; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/git | AI (phantom-deps): Config-referenced release plugin; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/npm | AI (phantom-deps): Config-referenced release plugin; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/github | AI (phantom-deps): Config-referenced release plugin; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/changelog | AI (phantom-deps): Config-referenced release plugin; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/commit-analyzer | AI (phantom-deps): Config-referenced release plugin; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@semantic-release/release-notes-generator | AI (phantom-deps): Config-referenced release plugin; stable pattern for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.3.5 | 3 / 17 | |
| 1.3.3 | 3 / 17 | |
| 1.3.2 | 10 / 10 | |
| 1.3.1 | 3 / 10 | |
| 1.3.0 | 3 / 10 | |
| 1.2.5 | 3 / 8 | |
| 1.2.3 | 3 / 8 | |
| 1.2.2 | 3 / 8 |
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.