@pulumiverse/scaleway
A Pulumi package for creating and managing Scaleway cloud resources.
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 |
|---|---|---|---|---|
| semgrep | semgrep:ssh-key-access | AI (semgrep): Fires on example/doc code showing ~/.ssh/id_rsa.pub as a sample input value, not credential harvesting. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires on `new Function(...)` where Function is the deprecated Pulumi resource class, not the JS built-in eval-like constructor. | ai | |
| provenance | no-provenance | AI (provenance): Established pulumiverse org package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1.53.0 | 1 / 3 | |
| 1.52.1 | 1 / 3 | |
| 1.52.0 | 1 / 3 | |
| 1.51.1 | 1 / 3 | |
| 1.51.0 | 1 / 3 | |
| 1.50.1 | 1 / 3 | |
| 1.50.0 | 1 / 3 | |
| 1.49.0 | 1 / 3 | |
| 1.48.1 | 1 / 3 | |
| 1.48.0 | 1 / 3 | |
| 1.47.0 | 1 / 3 | |
| 1.46.0 | 1 / 3 | |
| 1.45.0 | 1 / 3 | |
| 1.44.1 | 1 / 3 | |
| 1.44.0 | 1 / 3 | |
| 1.43.0 | 1 / 3 | |
| 1.42.0 | 1 / 3 | |
| 1.41.1 | 1 / 3 | |
| 1.41.0 | 1 / 3 | |
| 1.40.0 | 1 / 3 | |
| 1.39.0 | 1 / 3 | |
| 1.38.0 | 1 / 3 | |
| 1.37.0 | 1 / 3 | |
| 1.24.0 | 1 / 3 | |
| 1.23.0 | 1 / 3 | |
| 1.22.0 | 1 / 3 | |
| 1.21.1 | 1 / 3 | |
| 1.21.0 | 1 / 3 | |
| 1.20.0 | 1 / 3 | |
| 1.19.0 | 1 / 3 | |
| 1.18.0 | 1 / 3 | |
| 1.17.0 | 1 / 3 | |
| 1.16.0 | 1 / 3 |
v1.53.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.42.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.