← Home

@patternfly/patternfly-cli

npm

Patternfly cli for scaffolding projects, performing code mods, and running project related tasks

19
Versions
MIT
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

dgutridedlabrecqpatternfly-buildjeff-phillips-18mturleybennypmwczkylebuch8evwilkinschulj12nicolethoenheympzhawkinsdlabajausuliv

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): CLI tool intentionally passes process.env to subprocess for gh-pages build; expected pattern for this package. ai

Versions (showing 19 of 19)

Version Deps Published
1.2.15 5 / 22
1.2.14 5 / 19
1.2.13 5 / 19
1.2.12 5 / 19
1.2.11 5 / 19
1.2.10 5 / 19
1.2.9 5 / 19
1.2.8 5 / 19
1.2.7 5 / 19
1.2.6 5 / 19
1.2.5 5 / 19
1.2.4 5 / 19
1.2.3 5 / 19
1.2.2 5 / 19
1.2.1 5 / 19
1.2.0 5 / 19
1.1.0 5 / 19
1.0.4 5 / 19
1.0.3 5 / 19

v1.2.15

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

LOW No provenance attestation provenance

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

v1.2.14

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

LOW No provenance attestation provenance

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

v1.2.13

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

LOW No provenance attestation provenance

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

v1.2.12

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

LOW No provenance attestation provenance

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

v1.2.11

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.10

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.9

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.8

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.7

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.6

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.5

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.4

2 findings
HIGH env-spread: src/gh-pages.ts:204 semgrep

Spreading entire process.env into an object — may capture all secrets 202 | 203 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 204 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 205 | 206 | const pm = await getPackageManager(cwd);

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.

v1.2.3

2 findings
HIGH env-spread: src/gh-pages.ts:190 semgrep

Spreading entire process.env into an object — may capture all secrets 188 | 189 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 190 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 191 | 192 | const pm = await getPackageManager(cwd);

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.

v1.2.2

2 findings
HIGH env-spread: src/gh-pages.ts:190 semgrep

Spreading entire process.env into an object — may capture all secrets 188 | 189 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 190 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 191 | 192 | const pm = await getPackageManager(cwd);

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.

v1.2.1

2 findings
HIGH env-spread: src/gh-pages.ts:190 semgrep

Spreading entire process.env into an object — may capture all secrets 188 | 189 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 190 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 191 | 192 | const pm = await getPackageManager(cwd);

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.

v1.2.0

2 findings
HIGH env-spread: src/gh-pages.ts:190 semgrep

Spreading entire process.env into an object — may capture all secrets 188 | 189 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 190 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 191 | 192 | const pm = await getPackageManager(cwd);

LOW No provenance attestation provenance

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

v1.1.0

2 findings
HIGH env-spread: src/gh-pages.ts:190 semgrep

Spreading entire process.env into an object — may capture all secrets 188 | 189 | const { env: ghEnv, extraArgs } = getGithubPagesBuildArgs(pkg, publicPath); > 190 | const env = Object.keys(ghEnv).length ? { ...process.env, ...ghEnv } : process.env; 191 | 192 | const pm = await getPackageManager(cwd);

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.

v1.0.4

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.

v1.0.3

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.