@alicloud/gateway-pop
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Alibaba Cloud SDK package; lack of Sigstore provenance is consistent across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Alibaba Cloud SDK package; sparse metadata is a consistent pattern across the @alicloud namespace. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @alicloud SDK package generation pattern; not indicative of malice. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.5 | 12 / 7 | |
| 0.1.4 | 12 / 7 | |
| 0.1.3 | 12 / 7 | |
| 0.1.2 | 12 / 7 | |
| 0.0.9 | 11 / 7 | |
| 0.0.6 | 11 / 7 |
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.