@alicloud/pai-dlc20201203
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Generated SDK packages routinely add many source files per API version; stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Alibaba Cloud SDK client; sparse metadata is consistent across the entire SDK family. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.9.0 | 2 / 5 | |
| 1.8.0 | 2 / 5 | |
| 1.7.3 | 2 / 5 | |
| 1.7.2 | 2 / 5 | |
| 1.7.1 | 2 / 5 | |
| 1.7.0 | 2 / 5 | |
| 1.6.15 | 2 / 5 | |
| 1.6.14 | 2 / 5 | |
| 1.6.13 | 2 / 5 | |
| 1.6.12 | 2 / 5 | |
| 1.6.11 | 2 / 5 | |
| 1.6.10 | 2 / 5 | |
| 1.6.9 | 2 / 5 | |
| 1.6.8 | 2 / 5 | |
| 1.6.7 | 2 / 5 | |
| 1.6.6 | 2 / 5 | |
| 1.6.5 | 2 / 5 | |
| 1.6.4 | 2 / 5 | |
| 1.6.3 | 2 / 5 | |
| 1.6.2 | 2 / 5 | |
| 1.6.1 | 2 / 5 | |
| 1.6.0 | 2 / 5 | |
| 1.5.7 | 2 / 5 | |
| 1.5.6 | 2 / 5 | |
| 1.5.5 | 2 / 5 | |
| 1.5.4 | 2 / 5 | |
| 1.5.3 | 2 / 5 | |
| 1.5.2 | 2 / 5 |
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.3
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.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.