sezna/nps
NPM Package Scripts -- All the benefits of npm scripts without the cost of a bloated package.json and limits of json observed · 2026-08-28
Health v2 · maintenance only
26/100
- Activity 7
- Release rhythm 8
- Longevity 100
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: 3782
- days_rel: n/a
- days_push: 561
- n_releases_24m: 0
Adoption not part of the score
1450 stars · 95 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
nps (npm-package-scripts) is a CLI tool that lets you move npm scripts out of package. into a package-scripts.js or YAML file. It supports comments, nesting, and JavaScript logic for defining project scripts.
Use cases
- manage npm scripts without bloating package.
- add comments to project scripts
- organize nested script commands
- run concurrent build and test scripts
- define scripts with JavaScript logic instead of JSON
When to choose
- your package. scripts section has become an unmaintainable mess
- you need comments or variables in your scripts
- you want nested, namespaced script commands
When to avoid
- your project has only a few simple scripts
- your team prefers standard npm tooling with no extra dependency
Facets
cli-tool · maturity maintenance
cli build-tool workflow-automation developer-tools developer-tools cli cross-platform npm-scripts package-scripts package- task-runner javascript-config command-line automation javascript nodejs
2 sources
- readme: https://github.com/sezna/nps · fetched 2026-08-28 · d75e9d1c50a8
- registry_npm: https://registry.npmjs.org/nps · fetched 2026-08-29 · f663a324f82b
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| sezna/nps | main | 26 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem