@alicloud/sae20190506
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): IP address appears inside a JSDoc @example comment string, not in executable code — stable false positive for this SDK package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Alibaba Cloud SDK client; minimal README and no repo URL are consistent across the entire alicloud SDK family. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 2.12.4 | 2 / 5 | |
| 2.12.3 | 2 / 5 | |
| 2.12.2 | 2 / 5 | |
| 2.12.1 | 2 / 5 | |
| 2.12.0 | 2 / 5 | |
| 2.11.5 | 2 / 5 | |
| 2.11.4 | 2 / 5 | |
| 2.11.3 | 2 / 5 | |
| 2.11.2 | 2 / 5 | |
| 2.11.1 | 2 / 5 | |
| 2.11.0 | 2 / 5 | |
| 2.10.5 | 2 / 5 | |
| 2.10.4 | 2 / 5 | |
| 2.10.3 | 2 / 5 | |
| 2.10.2 | 2 / 5 | |
| 2.10.1 | 2 / 5 | |
| 2.10.0 | 2 / 5 | |
| 2.9.4 | 2 / 5 | |
| 2.9.3 | 2 / 5 | |
| 2.9.2 | 2 / 5 | |
| 2.9.1 | 2 / 5 | |
| 2.0.4 | 2 / 5 | |
| 2.0.3 | 2 / 5 | |
| 2.0.2 | 2 / 5 | |
| 2.0.1 | 5 / 5 | |
| 2.0.0 | 2 / 5 |
v2.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.