nx-config2
Supply chain provenance
Status for the latest visible version.
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
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): Config management tool; reading process.env is the intended core functionality, not a security risk. | ai | |
| phantom-deps | phantom-dep:micro-logs | AI (phantom-deps): micro-logs is listed as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.6.5 | 5 / 2 | |
| 3.0.0 | 1 / 2 | |
| 2.4.0 | 1 / 2 | |
| 2.3.1 | 1 / 2 | |
| 2.3.0 | 1 / 2 | |
| 2.2.2 | 1 / 2 | |
| 2.2.1 | 1 / 2 | |
| 2.2.0 | 1 / 2 | |
| 2.1.0 | 0 / 2 |
v3.6.5
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/nx-morpheus/nxconfig/blob/36bde0b8b43777e3a2559a3d5dc77d189df4dc2e/bin/nx-config2.js#L38 36 | 37 | // Parse environment variables > 38 | const env = { ...process.env }; 39 | 40 | if (options.env) {
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.