@alicloud/ecd20200930
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): AliCloud auto-generated SDK packages consistently lack repo/keywords; not a spam indicator for this family. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 2 / 5 | |
| 4.25.5 | 2 / 5 | |
| 4.25.4 | 2 / 5 | |
| 4.25.3 | 2 / 5 | |
| 4.25.2 | 2 / 5 | |
| 4.25.1 | 2 / 5 | |
| 4.25.0 | 2 / 5 | |
| 4.24.2 | 2 / 5 | |
| 4.24.1 | 2 / 5 | |
| 4.24.0 | 2 / 5 | |
| 4.23.4 | 2 / 5 | |
| 4.23.3 | 2 / 5 | |
| 4.23.2 | 2 / 5 | |
| 4.23.1 | 2 / 5 | |
| 4.23.0 | 2 / 5 | |
| 4.22.4 | 2 / 5 | |
| 4.22.3 | 2 / 5 | |
| 4.22.2 | 2 / 5 | |
| 4.22.1 | 2 / 5 | |
| 4.22.0 | 2 / 5 | |
| 4.21.2 | 2 / 5 | |
| 4.21.1 | 2 / 5 | |
| 4.21.0 | 2 / 5 | |
| 4.20.4 | 2 / 5 | |
| 4.20.3 | 2 / 5 | |
| 4.20.2 | 2 / 5 | |
| 4.20.1 | 2 / 5 | |
| 4.20.0 | 2 / 5 | |
| 4.19.3 | 2 / 5 | |
| 4.19.2 | 2 / 5 | |
| 4.19.1 | 2 / 5 | |
| 4.19.0 | 2 / 5 | |
| 4.18.0 | 2 / 5 | |
| 4.17.0 | 2 / 5 | |
| 4.16.3 | 2 / 5 | |
| 4.16.2 | 2 / 5 | |
| 4.16.1 | 2 / 5 | |
| 4.16.0 | 2 / 5 | |
| 4.15.0 | 2 / 5 | |
| 4.2.4 | 2 / 5 | |
| 4.2.3 | 2 / 5 | |
| 4.2.2 | 5 / 5 | |
| 4.2.1 | 5 / 5 | |
| 4.2.0 | 5 / 5 | |
| 4.1.2 | 5 / 5 | |
| 4.1.1 | 5 / 5 | |
| 4.1.0 | 5 / 5 | |
| 4.0.2 | 5 / 5 | |
| 4.0.1 | 5 / 5 | |
| 4.0.0 | 5 / 5 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.