@alicloud/aicontent20240611
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@alicloud/openapi-core | AI (dependencies): First-party Alibaba Cloud dependency; consistent across all @alicloud/* SDK packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated AliCloud SDK packages consistently lack repo URLs and keywords; not spam. | ai | |
| provenance | no-provenance | AI (provenance): AliCloud SDK packages are not published with Sigstore provenance; stable pattern for this publisher. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.4.2 | 2 / 5 | |
| 7.4.1 | 2 / 5 | |
| 7.4.0 | 2 / 5 | |
| 7.3.0 | 2 / 5 | |
| 7.2.0 | 2 / 5 | |
| 7.1.0 | 2 / 5 | |
| 7.0.2 | 2 / 5 | |
| 7.0.1 | 2 / 5 | |
| 7.0.0 | 2 / 5 | |
| 6.0.0 | 2 / 5 | |
| 5.0.0 | 2 / 5 |
v7.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.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.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.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.
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.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.