← Home

config

npm Repository Homepage

Configuration control for production node deployments

100
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

markstoslorenwestjdmarshall

Keywords

confconfigconfigurationnode-configconfig-nodeenvenvironment

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Documented maintainer transition from lorenwest to markstos for node-config; markstos has a long, clean track record with 130 approved packages. Not a compromise. ai
source-diff net-exec-file:parser.js AI (source-diff): parser.js is a legitimate config format dispatcher that lazy-loads optional libraries via require(). No actual network calls; dynamic require is by design for this package's pluggable parser architecture. ai
phantom-deps phantom-dep:json5 AI (phantom-deps): json5 is explicitly listed as a runtime dependency in package.json; the phantom-dep finding is a false positive for this package. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() is used inside a Proxy handler for config property access — idiomatic JS, not obfuscation. Stable false positive for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require() loads user-configured parser modules (TOML, YAML, etc.) — a documented core feature of node-config's pluggable parser system. ai

Versions (showing 100 of 127)

Show 2 prereleases
Version Deps Published
4.4.1 1 / 15
4.4.0 1 / 15
4.3.0 1 / 15
4.2.1 1 / 14
4.2.0 1 / 14
4.1.1 1 / 14
4.1.0 1 / 15
4.0.1 1 / 15
4.0.0 1 / 14
3.3.12 1 / 13
3.3.11 1 / 13
3.3.10 1 / 13
3.3.9 1 / 13
3.3.8 1 / 13
3.3.7 1 / 13
3.3.6 1 / 13
3.3.4 1 / 13
3.3.3 1 / 13
3.3.2 1 / 13
3.3.1 1 / 13
3.3.0 1 / 13
3.2.6 1 / 13
3.2.5 1 / 13
3.2.4 1 / 13
3.2.3 1 / 13
3.2.2 1 / 13
3.2.1 1 / 13
3.2.0 1 / 13
3.1.0 1 / 13
3.0.1 1 / 13
3.0.0 1 / 13
2.0.2 1 / 13
2.0.1 1 / 13
2.0.0 1 / 13
1.31.0 1 / 13
1.30.0 2 / 13
1.29.4 2 / 13
1.29.3 2 / 13
1.29.2 2 / 13
1.29.1 2 / 13
1.29.0 2 / 13
1.28.1 2 / 13
1.28.0 2 / 13
1.27.0 2 / 13
1.26.2 2 / 13
1.26.1 2 / 13
1.25.1 1 / 9
1.25.0 1 / 9
1.24.0 1 / 9
1.23.0 1 / 9
1.21.0 1 / 9
1.20.4 1 / 8
1.20.3 1 / 7
1.20.2 1 / 7
1.20.1 1 / 7
1.20.0 1 / 7
1.19.0 1 / 7
1.17.1 0 / 8
1.17.0 0 / 8
1.16.0 0 / 8
1.15.0 0 / 8
1.14.0 0 / 8
1.13.0 0 / 8
1.12.0 0 / 8
1.11.0 0 / 8
1.10.0 0 / 7
1.9.0 0 / 6
1.8.1 0 / 6
1.8.0 0 / 6
1.7.0 0 / 6
1.6.0 0 / 6
1.5.0 0 / 6
1.4.0 0 / 5
1.3.0 0 / 4
1.2.4 0 / 3
1.2.3 0 / 3
1.2.2 0 / 3
1.2.1 0 / 3
1.2.0 0 / 3
1.1.0 0 / 3
1.0.2 0 / 3
1.0.1 0 / 3
1.0.0 0 / 3
0.4.37 0 / 3
0.4.36 0 / 3
0.4.35 0 / 3
0.4.34 0 / 3
0.4.33 0 / 3
0.4.32 0 / 3
0.4.31 0 / 3
0.4.30 0 / 3
0.4.29 0 / 3
0.4.28 0 / 3
0.4.27 0 / 3
0.4.26 0 / 3
0.4.25 0 / 3
0.4.24 0 / 3
0.4.23 0 / 3
0.4.22 0 / 3
0.4.21 0 / 3
Showing 100 of 127 Next page →

v4.4.1

1 finding
LOW No provenance attestation provenance

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

v4.4.0

1 finding
LOW No provenance attestation provenance

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

v4.3.0

1 finding
LOW No provenance attestation provenance

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

v4.2.1

1 finding
LOW No provenance attestation provenance

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

v4.2.0

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

2 findings
HIGH Publisher changed: lorenwest → jdmarshall (on 2025-07-23) provenance

This version was published by a different npm account than previous versions on 2025-07-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v4.0.1

2 findings
HIGH Publisher changed: lorenwest → jdmarshall (on 2025-07-15) provenance

This version was published by a different npm account than previous versions on 2025-07-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v4.0.0

2 findings
HIGH Publisher changed: lorenwest → jdmarshall (on 2025-05-14) provenance

This version was published by a different npm account than previous versions on 2025-05-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.3.12

1 finding
LOW No provenance attestation provenance

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

v3.3.11

1 finding
LOW No provenance attestation provenance

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

v3.3.10

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: markstos → lorenwest (on 2024-01-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2024-01-09. This could indicate a legitimate maintainer transition or an account compromise.

v3.3.9

1 finding
LOW No provenance attestation provenance

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

v3.3.8

1 finding
LOW No provenance attestation provenance

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

v3.3.7

2 findings
HIGH Publisher changed: lorenwest → markstos (on 2022-01-11) provenance

This version was published by a different npm account than previous versions on 2022-01-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.3.6

1 finding
LOW No provenance attestation provenance

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

v3.3.4

1 finding
LOW No provenance attestation provenance

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

v3.3.3

1 finding
LOW No provenance attestation provenance

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

v3.3.2

1 finding
LOW No provenance attestation provenance

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

v3.3.1

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.6

1 finding
LOW No provenance attestation provenance

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

v3.2.5

1 finding
LOW No provenance attestation provenance

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

v3.2.4

1 finding
LOW No provenance attestation provenance

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

v3.2.3

1 finding
LOW No provenance attestation provenance

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

v3.2.2

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

2 findings
HIGH New file with network + code execution: parser.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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