@alicloud/rdsai20250507
English | [简体中文](README-CN.md) 
26
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
jacksontianfengmk2pagecaoaliyunsdkteamconsole-fe
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): AliCloud SDK packages routinely add many generated source files when new API operations are added; stable pattern for this publisher. | ai | |
| dependencies | unvetted-dep:@darabonba/typescript | AI (dependencies): Standard Alibaba Cloud SDK runtime dependency used across the entire aliyunsdkteam package family. | ai | |
| dependencies | unvetted-dep:@alicloud/openapi-core | AI (dependencies): Standard Alibaba Cloud SDK runtime dependency used across the entire aliyunsdkteam package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): AliCloud auto-generated SDK packages consistently lack repo URLs and keywords; not a spam/phishing indicator for this publisher family. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 2 / 5 | |
| 3.4.2 | 2 / 5 | |
| 3.4.1 | 2 / 5 | |
| 3.4.0 | 2 / 5 | |
| 3.3.0 | 2 / 5 | |
| 3.2.0 | 2 / 5 | |
| 3.1.0 | 2 / 5 | |
| 3.0.1 | 2 / 5 | |
| 3.0.0 | 2 / 5 | |
| 2.5.0 | 2 / 5 | |
| 2.4.2 | 2 / 5 | |
| 2.4.1 | 2 / 5 | |
| 2.4.0 | 2 / 5 | |
| 2.3.1 | 2 / 5 | |
| 2.3.0 | 2 / 5 | |
| 2.2.0 | 2 / 5 | |
| 2.1.1 | 2 / 5 | |
| 2.1.0 | 2 / 5 | |
| 2.0.4 | 2 / 5 | |
| 2.0.3 | 2 / 5 | |
| 2.0.2 | 2 / 5 | |
| 2.0.1 | 2 / 5 | |
| 2.0.0 | 2 / 5 | |
| 1.5.0 | 2 / 5 | |
| 1.4.1 | 2 / 5 | |
| 1.4.0 | 2 / 5 |
v3.5.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.