@alicloud/ecs20140526
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): ECS SDK regularly adds new source files per API version; growth is expected for this package. | ai | |
| dependencies | unvetted-dep:@alicloud/openapi-core | AI (dependencies): First-party Alibaba Cloud dependency; stable pattern across all versions of this SDK. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Alibaba Cloud auto-generated SDK packages consistently lack repo URLs and keywords; not spam. | ai | |
| provenance | no-provenance | AI (provenance): Established Alibaba Cloud SDK publisher; lack of Sigstore provenance is consistent across all their packages. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 7.9.2 | 2 / 5 | |
| 7.9.1 | 2 / 5 | |
| 7.9.0 | 2 / 5 | |
| 7.8.6 | 2 / 5 | |
| 7.8.5 | 2 / 5 | |
| 7.8.4 | 2 / 5 | |
| 7.8.3 | 2 / 5 | |
| 7.8.2 | 2 / 5 | |
| 7.8.1 | 2 / 5 | |
| 7.8.0 | 2 / 5 | |
| 7.7.6 | 2 / 5 | |
| 7.7.5 | 2 / 5 | |
| 7.7.4 | 2 / 5 | |
| 7.7.3 | 2 / 5 | |
| 7.7.2 | 2 / 5 | |
| 7.7.1 | 2 / 5 | |
| 7.7.0 | 2 / 5 | |
| 7.6.2 | 2 / 5 | |
| 7.6.1 | 2 / 5 | |
| 7.6.0 | 2 / 5 | |
| 7.5.4 | 2 / 5 | |
| 7.5.3 | 2 / 5 | |
| 7.5.2 | 2 / 5 | |
| 7.5.1 | 2 / 5 | |
| 7.5.0 | 2 / 5 | |
| 7.4.2 | 2 / 5 | |
| 7.4.1 | 2 / 5 | |
| 7.4.0 | 2 / 5 | |
| 7.3.0 | 2 / 5 |
v7.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.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.