@alicloud/sysom20231230
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): AliCloud auto-generated SDK packages consistently lack repo URLs and keywords; not indicative of spam or malice. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.18.0 | 2 / 5 | |
| 1.17.0 | 2 / 5 | |
| 1.16.2 | 2 / 5 | |
| 1.16.1 | 2 / 5 | |
| 1.16.0 | 2 / 5 | |
| 1.15.0 | 2 / 5 | |
| 1.14.0 | 2 / 5 | |
| 1.13.0 | 2 / 5 | |
| 1.12.1 | 2 / 5 | |
| 1.12.0 | 2 / 5 | |
| 1.11.0 | 2 / 5 | |
| 1.10.1 | 2 / 5 | |
| 1.10.0 | 2 / 5 | |
| 1.9.3 | 2 / 5 | |
| 1.9.2 | 2 / 5 | |
| 1.9.1 | 2 / 5 | |
| 1.9.0 | 2 / 5 | |
| 1.8.1 | 2 / 5 | |
| 1.8.0 | 2 / 5 | |
| 1.7.0 | 2 / 5 | |
| 1.6.0 | 2 / 5 | |
| 1.5.0 | 2 / 5 | |
| 1.4.0 | 2 / 5 | |
| 1.3.0 | 2 / 5 | |
| 1.2.1 | 5 / 5 | |
| 1.2.0 | 5 / 5 |
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.