@alicloud/rds20140815
English | [简体中文](README-CN.md) 
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Alibaba Cloud SDK client; sparse metadata is a stable pattern across this entire SDK family. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 15.9.0 | 2 / 5 | |
| 15.8.2 | 2 / 5 | |
| 15.8.1 | 2 / 5 | |
| 15.8.0 | 2 / 5 |
v15.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.