nodesecurity/nsp
node security platform command-line tool observed · 2026-08-28
Health v2 · maintenance only
10/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases archived
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4083
- days_rel: n/a
- days_push: 3040
- n_releases_24m: 0
Adoption not part of the score
1653 stars · 105 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
nsp is the Node Security Platform command-line tool that checks Node.js projects for known vulnerabilities in their dependencies, with CVSS-based filtering, thresholds, and pluggable output reporters. It was acquired by npm, Inc. in April 2018 and is no longer maintained; users should use `npm audit` instead.
Use cases
- scan node project dependencies for known vulnerabilities
- check npm packages against security advisories
- fail CI builds when dependencies have CVEs above a CVSS threshold
- output vulnerability reports as json or codeclimate in CI
When to choose
- you are maintaining a legacy project already configured to use nsp
When to avoid
- starting any new project - the tool is abandoned and the service was acquired by npm
- you want ongoing vulnerability database updates - use npm audit or Snyk instead
Facets
cli-tool · maturity abandoned
security vulnerability-scanning dependency-audit cli security developer-tools backend cli cross-platform npm node-security cvss deprecated acquired-by-npm nodejs
2 sources
- readme: https://github.com/nodesecurity/nsp · fetched 2026-08-28 · 79dc9de4ac6e
- registry_npm: https://registry.npmjs.org/nsp · fetched 2026-08-29 · 5df9ada18fc8
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| nodesecurity/nsp | main | 10 |
For agents
markdown · JSON · MCP: product_card(name="nodesecurity/nsp")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem