@alicloud/wss20211221
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 a spam/phishing indicator for this publisher. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.4.2 | 2 / 5 | |
| 1.4.1 | 2 / 5 | |
| 1.4.0 | 2 / 5 | |
| 1.3.6 | 2 / 5 | |
| 1.3.5 | 2 / 5 | |
| 1.3.4 | 2 / 5 | |
| 1.3.3 | 2 / 5 | |
| 1.3.2 | 2 / 5 | |
| 1.3.1 | 2 / 5 | |
| 1.3.0 | 2 / 5 | |
| 1.2.1 | 2 / 5 | |
| 1.2.0 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.0 | 6 / 5 |
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.