@highstate/gateway-api
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:@types/node-fetch | AI (phantom-deps): TypeScript types for build dependency; stable pattern in this package. | ai | |
| phantom-deps | phantom-dep:tmp | AI (phantom-deps): Legitimate build/config dependency in Pulumi resource package; stable pattern. | ai | |
| phantom-deps | phantom-dep:@types/tmp | AI (phantom-deps): TypeScript types for build dependency; stable pattern in this package. | ai | |
| phantom-deps | phantom-dep:node-fetch | AI (phantom-deps): Legitimate build/config dependency in Pulumi resource package; stable pattern. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript build tool; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Build-time dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:shell-quote | AI (phantom-deps): Build-time dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type definitions loaded by convention; stable for TypeScript packages. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 6 / 3 | |
| 0.9.31 | 8 / 5 | |
| 0.9.30 | 8 / 5 | |
| 0.9.29 | 8 / 5 | |
| 0.9.28 | 8 / 5 | |
| 0.9.27 | 8 / 5 | |
| 0.9.26 | 8 / 5 | |
| 0.9.25 | 8 / 5 | |
| 0.9.24 | 8 / 5 | |
| 0.9.23 | 8 / 5 | |
| 0.9.18 | 8 / 5 | |
| 0.9.16 | 8 / 5 | |
| 0.9.15 | 8 / 5 | |
| 0.9.14 | 8 / 5 | |
| 0.9.13 | 8 / 5 | |
| 0.9.12 | 8 / 5 | |
| 0.9.11 | 8 / 5 | |
| 0.9.10 | 8 / 5 | |
| 0.9.9 | 8 / 5 | |
| 0.9.8 | 8 / 5 | |
| 0.9.7 | 8 / 5 | |
| 0.9.6 | 8 / 5 | |
| 0.9.5 | 8 / 5 |
v0.9.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.