nsp Apache-2.0 46 versions

nsp

npm Repository Homepage

The Node Security (nodesecurity.io) command line interface

46

Versions

Apache-2.0

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

adam_baldwinandyet-opsgarnlf

Keywords

securitynspnodesecurity

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-removed	AI (maintainer-change): tomsteele's removal reflects an internal org change at ^Lift Security; adam_baldwin is the original author and primary maintainer. Not a hostile takeover signal.	ai	2026/04/24
phantom-deps	phantom-dep:subcommand	AI (phantom-deps): subcommand is a CLI framework dependency used via config/bin wiring rather than direct require(); consistent with CLI tool architecture.	ai	2026/04/24
dependencies	unvetted-dep:requiresafe-npm-utils	AI (dependencies): requiresafe-npm-utils is a first-party utility from the same organization (RequireSafe/^Lift Security) that publishes nsp; not a third-party risk.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change adam_baldwin→nlf in 2017 was a documented internal transition within the Node Security Project org. nlf has a strong track record (3581 approved packages). Not a suspicious takeover.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is an intentional plugin-loading pattern (nsp-preprocessor-*) in this security CLI tool; not attacker-controllable in normal usage.	ai	2026/04/23
phantom-deps	phantom-dep:yargs	AI (phantom-deps): yargs is properly declared in dependencies and is the expected CLI argument parser for this tool; false positive from the phantom-dep analyzer.	ai	2026/04/23

Versions (showing 46 of 46)

Version	Deps	Published
3.2.1	9 / 6	2018-02-15
3.2.0	9 / 6	2018-02-15
3.1.0	9 / 6	2017-11-06
3.0.0	9 / 6	2017-10-04
2.8.1	11 / 8	2017-09-27
2.8.0	11 / 8	2017-09-05
2.7.0	11 / 8	2017-07-26
2.6.3	11 / 8	2017-03-06
2.6.2	10 / 8	2016-10-03
2.6.1	10 / 8	2016-07-13
2.6.0	10 / 8	2016-07-07
2.5.0	10 / 8	2016-06-23
2.4.0	10 / 8	2016-05-04
2.3.3	10 / 8	2016-05-10
2.3.2	10 / 8	2016-04-26
2.3.1	10 / 8	2016-04-21
2.3.0	10 / 8	2016-03-30
2.2.2	10 / 8	2016-03-28
2.2.1	10 / 8	2016-03-09
2.2.0	10 / 8	2015-12-21
2.1.0	10 / 8	2015-12-02
2.0.2	9 / 8	2015-11-06
2.0.1	9 / 6	2015-11-03
2.0.0	9 / 6	2015-10-31
1.1.0	14 / 8	2015-08-22
1.0.3	14 / 8	2015-06-22
1.0.2	14 / 8	2015-06-22
1.0.1	14 / 8	2015-03-10
1.0.0	14 / 8	2015-01-21
0.6.1	15 / 8	2015-01-21
0.6.0	15 / 7	2015-01-21
0.5.2	15 / 5	2014-12-07
0.4.2	15 / 2	2014-10-03
0.4.1	15 / 2	2014-09-20
0.4.0	15 / 2	2014-09-17
0.3.0	15 / 2	2014-09-16
0.2.8	14 / 2	2014-09-12
0.2.6	13 / 2	2014-09-09
0.2.5	12 / 2	2014-09-05
0.2.4	12 / 2	2014-09-03
0.2.3	12 / 2	2014-08-26
0.2.2	12 / 2	2014-08-21
0.2.1	15 / 1	2014-08-02
0.2.0	15 / 1	2014-08-01
0.0.2	11 / 1	2014-03-17
0.0.1	11 / 1	2014-03-17

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

1 finding

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.0

2 findings

HIGH Publisher changed: adam_baldwin → nlf (on 2017-10-04) provenance

This version was published by a different npm account than previous versions on 2017-10-04. 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.

v2.8.1

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: nlf → adam_baldwin (on 2017-09-27) provenance

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

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.3

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: gar → nlf (on 2017-03-06) provenance

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

v2.6.2

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: nlf → gar (on 2016-10-03) provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.3

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: adam_baldwin → nlf (on 2016-05-10) provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.1

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: nlf → adam_baldwin (on 2016-04-21) provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

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: adam_baldwin → nlf (on 2016-03-09) provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.0

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: nlf → adam_baldwin (on 2015-12-02) provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

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: adam_baldwin → nlf (on 2015-11-03) provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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