@jsdevtools/npm-publish
Fast, easy publishing to NPM
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into child_process.spawn options is the standard pattern for this npm CLI wrapper tool; it passes env to subprocess, not to external endpoints. Stable false positive for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.1.5 | 5 / 19 | |
| 4.1.4 | 5 / 19 | |
| 4.1.3 | 5 / 19 | |
| 4.1.2 | 5 / 19 | |
| 4.1.1 | 5 / 19 | |
| 4.1.0 | 5 / 19 | |
| 4.0.1 | 5 / 19 | |
| 4.0.0 | 5 / 19 | |
| 3.1.1 | 4 / 24 | |
| 3.1.0 | 4 / 24 | |
| 3.0.1 | 4 / 24 | |
| 3.0.0 | 4 / 24 | |
| 2.2.2 | 4 / 24 | |
| 2.2.1 | 4 / 24 | |
| 2.2.0 | 4 / 25 | |
| 2.1.0 | 4 / 25 | |
| 2.0.0 | 4 / 25 | |
| 1.4.3 | 4 / 18 | |
| 1.4.2 | 4 / 18 | |
| 1.4.1 | 4 / 18 | |
| 1.4.0 | 4 / 18 | |
| 1.3.0 | 4 / 18 | |
| 1.2.0 | 4 / 18 | |
| 1.1.2 | 4 / 18 | |
| 1.1.0 | 4 / 21 | |
| 1.0.13 | 4 / 21 | |
| 1.0.12 | 4 / 21 | |
| 1.0.11 | 4 / 21 | |
| 1.0.10 | 0 / 23 | |
| 1.0.9 | 0 / 24 |
v4.1.5
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/JS-DevTools/npm-publish/blob/0fd2f4369c5d6bcfcde6091a7c527d810b9b5c3f/lib/npm/call-npm-cli.js#L51 49 | let stderr = ""; 50 | const npm = childProcess.spawn(NPM, commandArguments, { > 51 | env: { ...process.env, ...environment }, 52 | shell: IS_WINDOWS, 53 | });
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/JS-DevTools/npm-publish/blob/0fd2f4369c5d6bcfcde6091a7c527d810b9b5c3f/src/npm/call-npm-cli.ts#L108 106 | 107 | const npm = childProcess.spawn(NPM, commandArguments, { > 108 | env: { ...process.env, ...environment }, 109 | shell: IS_WINDOWS, 110 | });
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-23. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.