config MIT 51 versions

config

npm Repository Homepage

Configuration control for production node deployments

51

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.

Source	Rule	Reason	Accepted by	When
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/23
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	2026/04/23

Versions (showing 51 of 129)

Hide prereleases View all versions

Version	Deps	Published
4.4.1	1 / 15	2026-02-25
4.4.0	1 / 15	2026-02-22
4.3.0	1 / 15	2026-02-12
4.2.1	1 / 14	2026-02-10
4.2.0	1 / 14	2026-01-15
4.1.1	1 / 14	2025-08-15
4.1.0	1 / 15	2025-07-23
4.0.1	1 / 15	2025-07-15
4.0.0	1 / 14	2025-05-14
3.3.12	1 / 13	2024-06-25
3.3.11	1 / 13	2024-02-01
3.3.10	1 / 13	2024-01-09
3.3.9	1 / 13	2023-01-17
3.3.8	1 / 13	2022-09-09
3.3.7	1 / 13	2022-01-11
3.3.6	1 / 13	2021-03-08
3.3.4	1 / 13	2021-02-27
3.3.3	1 / 13	2020-11-26
3.3.2	1 / 13	2020-09-24
3.3.1	1 / 13	2020-03-25
3.3.0	1 / 13	2020-02-27
3.2.6	1 / 13	2020-02-21
3.2.5	1 / 13	2020-01-16
3.2.4	1 / 13	2019-10-25
3.2.3	1 / 13	2019-10-03
3.2.2	1 / 13	2019-07-21
3.2.1	1 / 13	2019-07-18
3.2.0	1 / 13	2019-07-11
3.1.0	1 / 13	2019-04-07
3.0.1	1 / 13	2018-12-17
3.0.0	1 / 13	2018-11-20
2.0.2	1 / 13	2018-11-20
2.0.1	1 / 13	2018-07-30
2.0.0	1 / 13	2018-07-27
1.31.0	1 / 13	2018-07-23
1.30.0	2 / 13	2018-02-26
1.29.4	2 / 13	2018-02-04
1.29.3	2 / 13	2018-02-03
1.29.2	2 / 13	2018-01-13
1.29.1	2 / 13	2018-01-07
1.29.0	2 / 13	2017-12-26
1.28.1	2 / 13	2017-11-09
1.28.0	2 / 13	2017-11-07
1.27.0	2 / 13	2017-10-17
1.26.2	2 / 13	2017-08-12
1.26.1	2 / 13	2017-05-03
1.25.1	1 / 9	2017-02-01
1.25.0	1 / 9	2017-01-31
1.24.0	1 / 9	2016-11-02
1.23.0	1 / 9	2016-11-02
1.21.0	1 / 9	2016-06-01

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.