@alicloud/cms20240330
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 Alibaba Cloud SDK; large file count increases are normal across API versions. | ai | |
| dependencies | unvetted-dep:@alicloud/openapi-core | AI (dependencies): First-party Alibaba Cloud core library; stable dependency for this SDK family. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established SDK publisher with 12 approved packages; dormancy reflects SDK release cadence, not takeover. | ai | |
| provenance | no-provenance | AI (provenance): Established Alibaba Cloud SDK publisher; lack of Sigstore provenance is consistent across all versions of this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): AliCloud SDK packages consistently lack repo/homepage metadata and have sparse READMEs; this is a family-wide pattern, not a spam indicator. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 9.2.2 | 2 / 5 | |
| 9.2.1 | 2 / 5 | |
| 9.2.0 | 2 / 5 | |
| 9.1.0 | 2 / 5 | |
| 9.0.1 | 2 / 5 | |
| 9.0.0 | 2 / 5 | |
| 8.1.0 | 2 / 5 | |
| 8.0.1 | 2 / 5 | |
| 8.0.0 | 2 / 5 | |
| 7.1.0 | 2 / 5 | |
| 7.0.2 | 2 / 5 | |
| 7.0.1 | 2 / 5 | |
| 7.0.0 | 2 / 5 | |
| 6.5.0 | 2 / 5 | |
| 6.4.0 | 2 / 5 | |
| 6.3.0 | 2 / 5 | |
| 6.2.4 | 2 / 5 | |
| 6.2.3 | 2 / 5 | |
| 6.2.2 | 2 / 5 | |
| 6.2.1 | 2 / 5 | |
| 6.2.0 | 2 / 5 | |
| 6.1.0 | 2 / 5 | |
| 6.0.1 | 2 / 5 | |
| 6.0.0 | 2 / 5 | |
| 5.1.0 | 2 / 5 | |
| 5.0.0 | 2 / 5 | |
| 4.2.0 | 2 / 5 | |
| 4.1.0 | 2 / 5 | |
| 4.0.0 | 2 / 5 | |
| 3.6.1 | 2 / 5 | |
| 3.6.0 | 2 / 5 | |
| 3.5.0 | 2 / 5 | |
| 3.4.0 | 2 / 5 | |
| 3.3.0 | 2 / 5 | |
| 3.2.5 | 2 / 5 |
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.