@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 — 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 |
|---|---|---|---|---|
| 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 27 of 27)
| 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 |
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.