@alicloud/csas20230120
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP appears only in JSDoc @example comments as a placeholder URL, not in executable network code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Alibaba Cloud SDK packages consistently lack repo/keywords and have link-dump READMEs; not indicative of malice. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 1.17.0 | 2 / 5 | |
| 1.16.0 | 2 / 5 | |
| 1.15.0 | 2 / 5 | |
| 1.14.22 | 2 / 5 | |
| 1.14.21 | 2 / 5 | |
| 1.14.20 | 2 / 5 | |
| 1.14.19 | 2 / 5 | |
| 1.14.18 | 2 / 5 | |
| 1.14.17 | 2 / 5 | |
| 1.14.16 | 2 / 5 | |
| 1.14.15 | 2 / 5 | |
| 1.14.14 | 2 / 5 | |
| 1.14.13 | 2 / 5 | |
| 1.14.12 | 2 / 5 | |
| 1.14.11 | 2 / 5 | |
| 1.14.10 | 2 / 5 | |
| 1.14.9 | 2 / 5 | |
| 1.14.8 | 2 / 5 | |
| 1.14.7 | 2 / 5 | |
| 1.14.6 | 2 / 5 | |
| 1.14.5 | 2 / 5 | |
| 1.14.4 | 2 / 5 | |
| 1.14.3 | 2 / 5 | |
| 1.14.2 | 2 / 5 | |
| 1.14.1 | 2 / 5 | |
| 1.14.0 | 2 / 5 | |
| 1.13.0 | 2 / 5 | |
| 1.12.2 | 2 / 5 | |
| 1.12.1 | 2 / 5 | |
| 1.12.0 | 2 / 5 | |
| 1.11.2 | 2 / 5 | |
| 1.11.1 | 2 / 5 | |
| 1.11.0 | 2 / 5 | |
| 1.10.0 | 5 / 5 | |
| 1.9.3 | 5 / 5 | |
| 1.9.2 | 5 / 5 | |
| 1.9.1 | 5 / 5 | |
| 1.9.0 | 5 / 5 | |
| 1.8.0 | 5 / 5 | |
| 1.7.2 | 5 / 5 | |
| 1.7.1 | 5 / 5 | |
| 1.7.0 | 5 / 5 | |
| 1.6.0 | 5 / 5 | |
| 1.5.1 | 5 / 5 | |
| 1.3.0 | 5 / 5 | |
| 1.2.1 | 5 / 5 | |
| 1.2.0 | 5 / 5 | |
| 1.1.2 | 5 / 5 | |
| 1.1.1 | 5 / 5 | |
| 1.1.0 | 5 / 5 | |
| 1.0.1 | 5 / 5 |
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.