@alicloud/openapi-util
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): Alibaba Cloud SDK; sparse metadata is normal for corporate-published packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Corporate SDK pattern; missing description is stable for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 4 / 7 | |
| 0.3.2 | 4 / 7 | |
| 0.3.1 | 4 / 7 | |
| 0.3.0 | 4 / 7 | |
| 0.2.9 | 4 / 7 | |
| 0.2.8 | 4 / 7 | |
| 0.2.7 | 4 / 7 | |
| 0.2.6 | 4 / 7 | |
| 0.2.5 | 4 / 7 | |
| 0.2.4 | 4 / 7 | |
| 0.2.3 | 4 / 7 | |
| 0.2.2 | 4 / 7 | |
| 0.2.1 | 4 / 7 | |
| 0.2.0 | 4 / 7 | |
| 0.1.3 | 3 / 7 | |
| 0.1.2 | 3 / 7 | |
| 0.1.1 | 3 / 7 | |
| 0.1.0 | 3 / 7 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aliyunsdkteam) than the most recent previously approved version (pagecao) on 2023-01-10, but aliyunsdkteam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aliyunsdkteam) than the most recent previously approved version (pagecao) on 2022-11-08, but aliyunsdkteam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pagecao) than the most recent previously approved version (aliyunsdkteam) on 2022-06-07, but pagecao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pagecao) than the most recent previously approved version (aliyunsdkteam) on 2022-01-17, but pagecao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aliyunsdkteam) than the most recent previously approved version (pagecao) on 2021-09-07, but aliyunsdkteam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aliyunsdkteam) than the most recent previously approved version (pagecao) on 2021-03-30, but aliyunsdkteam is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pagecao) than the most recent previously approved version (aliyunsdkteam) on 2020-11-26, but pagecao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.