ali-oss
aliyun oss(object storage service) node client
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Gap reflects unimported npm versions between our last snapshot and this one, not inactivity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): lodash/qs are mainstream, well-vetted utility deps, not a supply-chain vector here. | ai | |
| phantom-deps | phantom-dep:mz-modules | AI (phantom-deps): mz-modules is declared as a runtime dep and used indirectly; phantom-dep is a false positive here. | ai | |
| dependencies | unvetted-dep:utility | AI (dependencies): Established Alibaba utility package; stable dependency for this SDK. | ai | |
| dependencies | unvetted-dep:sdk-base | AI (dependencies): Alibaba sdk-base is a standard base class used across Alibaba Node.js SDKs. | ai | |
| dependencies | unvetted-dep:stream-wormhole | AI (dependencies): Small, well-known stream utility; stable dependency for this SDK. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes base64-encoded error messages from Alibaba OSS API response headers (x-oss-err). This is documented OSS API behavior, not a malicious payload. | ai | |
| phantom-deps | phantom-dep:end-or-error | AI (phantom-deps): end-or-error is a declared runtime dependency; phantom detection is a false positive for this SDK. | ai | |
| phantom-deps | phantom-dep:stream-http | AI (phantom-deps): stream-http is a declared runtime dependency used in browser shims (referenced in browser field of package.json); not a security concern. | ai | |
| phantom-deps | phantom-dep:destroy | AI (phantom-deps): destroy is a declared runtime dependency used in browser shims or transitively; not a security concern for this SDK. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 6.23.0 | 25 / 64 | |
| 6.22.0 | 25 / 64 | |
| 6.21.0 | 25 / 63 | |
| 6.18.1 | 23 / 60 | |
| 6.17.1 | 24 / 50 |
v6.22.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 (fengmk2) than the most recent previously approved version (peizerao) on 2024-12-03, but fengmk2 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.
v6.21.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 (fengmk2) than the most recent previously approved version (peizerao) on 2024-08-16, but fengmk2 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.
v6.18.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 (fengmk2) than the most recent previously approved version (peizerao) on 2023-09-11, but fengmk2 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.
v6.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.