@alicloud/emr-serverless-spark20230808
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@alicloud/openapi-core | AI (dependencies): Sibling Alibaba Cloud SDK package; expected internal dependency across this SDK family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Alibaba Cloud SDK package; sparse metadata is a known pattern across the entire @alicloud/* namespace. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.25.0 | 2 / 5 | |
| 1.24.0 | 2 / 5 | |
| 1.23.0 | 2 / 5 | |
| 1.22.0 | 2 / 5 | |
| 1.21.1 | 2 / 5 | |
| 1.21.0 | 2 / 5 | |
| 1.20.1 | 2 / 5 | |
| 1.20.0 | 2 / 5 | |
| 1.19.2 | 2 / 5 | |
| 1.19.1 | 2 / 5 | |
| 1.19.0 | 2 / 5 | |
| 1.18.0 | 2 / 5 | |
| 1.17.1 | 2 / 5 | |
| 1.17.0 | 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.3 | 2 / 5 | |
| 1.10.2 | 2 / 5 | |
| 1.10.1 | 2 / 5 | |
| 1.10.0 | 2 / 5 | |
| 1.9.0 | 5 / 5 | |
| 1.8.1 | 5 / 5 | |
| 1.8.0 | 5 / 5 | |
| 1.7.0 | 5 / 5 | |
| 1.6.0 | 5 / 5 | |
| 1.5.0 | 5 / 5 | |
| 1.4.2 | 5 / 5 | |
| 1.4.1 | 5 / 5 | |
| 1.4.0 | 5 / 5 | |
| 1.3.0 | 5 / 5 | |
| 1.2.0 | 5 / 5 | |
| 1.1.0 | 5 / 5 | |
| 1.0.1 | 5 / 5 | |
| 1.0.0 | 5 / 5 |
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.