@alicloud/alidns20150109
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 client; sparse metadata is a known pattern across this publisher's packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.6.0 | 2 / 5 | |
| 4.5.0 | 2 / 5 | |
| 4.4.1 | 2 / 5 | |
| 4.4.0 | 2 / 5 | |
| 4.3.6 | 2 / 5 | |
| 4.3.5 | 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.1 | 2 / 5 | |
| 4.1.0 | 2 / 5 | |
| 4.0.0 | 2 / 5 | |
| 3.6.0 | 2 / 5 |
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.