@alicloud/gpdb20160503
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@alicloud/openapi-core | AI (dependencies): Same Alibaba Cloud org scope; consistent with this SDK's dependency pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Alibaba Cloud SDK package; missing repo/keywords/readme is a stable pattern across this entire SDK family. | ai | |
| phantom-deps | phantom-dep:@alicloud/credentials | AI (phantom-deps): @alicloud/credentials is a declared runtime dep in the same org scope; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 3 / 5 | |
| 3.4.1 | 3 / 5 | |
| 3.4.0 | 3 / 5 | |
| 3.3.0 | 3 / 5 | |
| 3.2.2 | 3 / 5 | |
| 3.2.1 | 3 / 5 |
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.