@alicloud/fc20230330
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): Auto-generated Alibaba Cloud SDK; sparse README and missing repo/keywords are structural artifacts of their SDK generation pipeline, not spam indicators. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 4.7.9 | 2 / 5 | |
| 4.7.8 | 2 / 5 | |
| 4.7.7 | 2 / 5 | |
| 4.7.6 | 2 / 5 | |
| 4.7.5 | 2 / 5 | |
| 4.7.4 | 2 / 5 | |
| 4.7.3 | 2 / 5 | |
| 4.7.2 | 2 / 5 | |
| 4.7.1 | 2 / 5 | |
| 4.7.0 | 2 / 5 | |
| 4.6.8 | 2 / 5 | |
| 4.6.7 | 2 / 5 | |
| 4.6.6 | 2 / 5 | |
| 4.6.5 | 2 / 5 | |
| 4.6.4 | 2 / 5 | |
| 4.6.3 | 2 / 5 | |
| 4.6.2 | 2 / 5 | |
| 4.6.1 | 2 / 5 | |
| 4.6.0 | 2 / 5 | |
| 4.5.0 | 2 / 5 | |
| 4.4.1 | 2 / 5 | |
| 4.4.0 | 2 / 5 | |
| 4.3.4 | 2 / 5 | |
| 4.3.3 | 2 / 5 | |
| 4.3.2 | 2 / 5 | |
| 4.3.1 | 2 / 5 | |
| 4.3.0 | 2 / 5 | |
| 4.2.0 | 2 / 5 | |
| 4.1.10 | 2 / 5 | |
| 4.1.9 | 2 / 5 | |
| 4.1.8 | 2 / 5 | |
| 4.1.7 | 2 / 5 | |
| 4.1.6 | 5 / 5 | |
| 4.1.5 | 5 / 5 | |
| 4.1.4 | 5 / 5 | |
| 4.1.3 | 5 / 5 | |
| 4.1.2 | 5 / 5 | |
| 4.1.1 | 5 / 5 |
v4.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.