← Home

@pulumi/alicloud

A Pulumi package for creating and managing AliCloud resources.

6
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 gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

joeduffypulumi-bot

Keywords

pulumialicloud

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:credential-dir-access AI (semgrep): Fires on doc comments referencing ~/.kube/config paths, not actual credential harvesting code. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IP appears in JSDoc example YAML snippets, not in executable network requests. ai
semgrep semgrep:new-function-constructor AI (semgrep): Pattern matches `new Function(name, state, opts)` which is a class constructor call, not dynamic code eval. ai
provenance no-provenance AI (provenance): Established Pulumi provider; lack of Sigstore provenance is consistent across all prior versions. ai

Versions (showing 6 of 6)

Version Deps Published
3.103.0 1 / 2
3.102.0 1 / 2
3.101.0 1 / 2
3.100.0 1 / 2
3.99.0 1 / 2
3.98.0 1 / 2

v3.103.0

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.102.0

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.100.0

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.99.0

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.98.0

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.