@huaweicloud/huaweicloud-sdk-pangulargemodels
Huaweicloud SDK for pangulargemodels
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:@huaweicloud/huaweicloud-sdk-core | AI (dependencies): First-party Huawei Cloud SDK core dependency; stable pattern across all versions of this package family. | ai | |
| provenance | no-provenance | AI (provenance): HuaweiCloud SDK packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 13 of 113)
| Version | Deps | Published |
|---|---|---|
| 3.1.106 | 1 / 2 | |
| 3.1.105 | 1 / 2 | |
| 3.1.104 | 1 / 2 | |
| 3.1.103 | 1 / 2 | |
| 3.1.102 | 1 / 2 | |
| 3.1.101 | 1 / 2 | |
| 3.1.100 | 1 / 2 | |
| 3.1.99 | 1 / 2 | |
| 3.1.98 | 1 / 2 | |
| 3.1.97 | 1 / 2 | |
| 3.1.96 | 1 / 2 | |
| 3.1.95 | 1 / 2 | |
| 3.1.94 | 1 / 2 |
v3.1.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.105
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.104
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.103
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.99
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.