← Home

@huaweicloud/huaweicloud-sdk-identitycenterscim

npm Repository Homepage

Huaweicloud SDK for identitycenterscim

30
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

huaweicloud_adminchen_11koomsg

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Huawei Cloud SDK packages consistently publish without Sigstore provenance; stable false positive for this publisher family. ai

Versions (showing 30 of 30)

Version Deps Published
3.1.207 1 / 2
3.1.206 1 / 2
3.1.205 1 / 2
3.1.204 1 / 2
3.1.203 1 / 2
3.1.202 1 / 2
3.1.201 1 / 2
3.1.200 1 / 2
3.1.199 1 / 2
3.1.198 1 / 2
3.1.197 1 / 2
3.1.196 1 / 2
3.1.195 1 / 2
3.1.194 1 / 2
3.1.193 1 / 2
3.1.188 1 / 2
3.1.183 1 / 2
3.1.181 1 / 2
3.1.180 1 / 2
3.1.176 1 / 2
3.1.175 1 / 2
3.1.172 1 / 2
3.1.166 1 / 2
3.1.161 1 / 2
3.1.154 1 / 2
3.1.148 1 / 2
3.1.146 1 / 2
3.1.145 1 / 2
3.1.144 1 / 2
3.1.143 1 / 2

v3.1.207

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.206

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.205

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.204

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.203

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.202

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.146

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.145

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.144

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.143

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.