← Home

@pulumi/github

npm Repository Homepage

A Pulumi package for creating and managing github cloud resources.

33
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

joeduffypulumi-bot

Keywords

pulumigithub

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:ssh-key-access AI (semgrep): Fires on JSDoc example code demonstrating the userSshKey resource API; not credential theft. Stable false positive for this package. ai

Versions (showing 33 of 33)

Version Deps Published
6.14.1 1 / 3
6.14.0 1 / 3
6.13.1 1 / 3
6.13.0 1 / 3
6.12.2 1 / 3
6.12.1 1 / 3
6.12.0 1 / 3
6.11.0 1 / 3
6.10.1 1 / 3
6.10.0 1 / 3
6.9.1 1 / 3
6.9.0 1 / 3
6.8.1 1 / 3
6.8.0 1 / 3
6.7.4 1 / 3
6.7.3 1 / 3
6.7.2 1 / 3
6.7.1 1 / 3
6.7.0 1 / 3
6.6.0 1 / 3
6.5.0 1 / 3
6.4.0 1 / 3
6.3.2 1 / 3
6.3.1 1 / 3
6.3.0 1 / 3
6.2.5 1 / 3
6.2.3 1 / 3
6.2.2 1 / 3
6.2.1 1 / 3
6.2.0 1 / 3
6.1.0 1 / 3
6.0.1 1 / 3
6.0.0 1 / 3

v6.14.1

1 finding
LOW No provenance attestation provenance

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

v6.7.0

1 finding
LOW No provenance attestation provenance

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

v6.6.0

1 finding
LOW No provenance attestation provenance

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

v6.5.0

1 finding
LOW No provenance attestation provenance

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

v6.4.0

1 finding
LOW No provenance attestation provenance

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

v6.3.2

1 finding
LOW No provenance attestation provenance

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

v6.3.1

1 finding
LOW No provenance attestation provenance

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

v6.3.0

1 finding
LOW No provenance attestation provenance

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

v6.2.5

1 finding
LOW No provenance attestation provenance

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

v6.2.3

1 finding
LOW No provenance attestation provenance

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

v6.2.2

1 finding
LOW No provenance attestation provenance

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

v6.2.1

1 finding
LOW No provenance attestation provenance

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

v6.2.0

1 finding
LOW No provenance attestation provenance

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

v6.1.0

1 finding
LOW No provenance attestation provenance

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

v6.0.1

1 finding
LOW No provenance attestation provenance

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

v6.0.0

1 finding
LOW No provenance attestation provenance

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