@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, so a manually published version cannot be tied back to a reviewed commit.
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 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 15.9.0 | 2 / 5 | |
| 15.8.2 | 2 / 5 | |
| 15.8.1 | 2 / 5 | |
| 15.8.0 | 2 / 5 | |
| 15.7.1 | 2 / 5 | |
| 15.7.0 | 2 / 5 | |
| 15.6.0 | 2 / 5 | |
| 15.5.1 | 2 / 5 | |
| 15.5.0 | 2 / 5 | |
| 15.4.0 | 2 / 5 | |
| 15.3.0 | 2 / 5 | |
| 15.2.0 | 2 / 5 | |
| 15.1.2 | 2 / 5 | |
| 15.1.1 | 2 / 5 | |
| 15.1.0 | 2 / 5 | |
| 15.0.0 | 2 / 5 | |
| 14.2.0 | 2 / 5 | |
| 14.1.0 | 2 / 5 | |
| 14.0.2 | 2 / 5 | |
| 14.0.1 | 2 / 5 | |
| 14.0.0 | 2 / 5 | |
| 13.1.0 | 2 / 5 | |
| 13.0.1 | 2 / 5 | |
| 13.0.0 | 2 / 5 |
v15.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.