npq
v3.27.0 open-sourceThe section your link pointed to isn't on npq's page any more, so we've brought you to the top.
npq audits npm packages before installation by checking vulnerabilities, package age, download count, README, license, and install scripts.
NPQ_ALLOW_NON_INTERACTIVE_INSTALL=true npq install express npq install express --allow-non-interactive-install npq install express --json npq install @company/tool --registry=https://artifactory.example.com/artifactory/api/npm/npm-virtual/ npq --dormant-maintainers npq <package-name> --signal-type archived npq --no-continue install <package-name> SNYK_API_URL=https://snyk.company.io/api/v1 SNYK_TOKEN=sk_abc123 npq check package-lock.json npq install --plain npq express --version-pattern ">=2.0.0" npq check --version-maturity eol npq check --version-maturity lts npq --top npq marshall <package> npq install npq install --marshal npq install <package> --no-marshalls
Summary
npq is an open-source command-line tool, free to use, that audits npm packages for vulnerabilities, suspicious scripts, typosquattingtyposquattingUsing a name close to a trusted domain or software package to catch spelling mistakes. Attackers use it to lure people or installers to a malicious lookalike., and other risk signals before they're installed, typically invoked as npx npq install <package> in place of a plain npm install. It's aimed at application developers and the platform or security engineers who set install-time policy for a team, and it fits naturally into CI, where its --json flag produces a versioned, machine-readable audit report for pipelines or SIEMSIEMSecurity information and event management, collecting logs from many systems and correlating events to find suspicious activity. Analysts use it to investigate alerts and incidents. ingestion without proceeding to install. It supports authenticated private and custom registries, reading standard npm registry configuration for auth and TLS, and it corroborates expired-domain warnings against RDAPRDAPA JSON-based protocol for querying domain and IP registration data, standardized by the IETF as a modern replacement for WHOIS, giving cyber tools structured, machine-readable ownership and contact lookups. rather than relying on DNS alone. It sits in the appsec space, addressing dependency risk at install time rather than after the fact, and with 30 contributors, 82 commits and a release 29 days ago, it's under active development.
npq audits npm packages before installation by checking vulnerabilities, package age, download count, README, license, and install scripts.
How npq helps
Is this package safe to install before it lands in my project?
runs vulnerability, suspicious-script, and typosquatting checks against the package and its metadata, and reports the verdict before anything is installed
Is that expired-looking maintainer domain actually abandoned?
flags the domain only when DNS returns no record and the authoritative RDAP registry independently confirms no active registration, cutting false alarms from DNS lookups alone
Which packages need a human to look closer, and what should they check next?
for packages that fail on version maturity, names the highest older version published outside the recency window as a concrete candidate to audit instead
Can my pipeline block on this without a person watching the prompts?
emits a versioned JSON report that skips interactive prompts and stops before install, so CI or a SIEM can consume the result programmatically
Will this run safely inside an automated or headless step without hanging on a prompt?
detects non-interactive and coding-agent environments and switches to JSON-safe parsing and output automatically, or can be explicitly authorized to proceed with install
Does this still work against my private or internal package registry?
reads the standard npm registry configuration for auth, proxies, TLS, and client certs, and routes metadata, signing, and provenance lookups through that same authenticated registry, reporting capabilities as not evaluated when the registry doesn't support them
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for npq, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail npq puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
40 entries
No entries match these filters.
- August 20264
- July 20264
- April 20262
- December 20251
- November 20251
- October 20251
- August 20252
- July 20252
- June 20253
- November 20231
- September 20234
- January 20231
- October 20201
- September 20201
- December 20191
- June 20182
- April 20181
- January 20185
- December 20173
Project health
Issue, contributor and maintainer activity in lirantal/npq, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 4 ±0 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 83% of issues opened, last 12 months
- Median time to close 55 days first maintainer reply 4.1 days
- Open backlog 5 of 124 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 5
- Contributors / month 0
- Commits / month 0
- Stars 1,795
- bugs 21%
- features 32%
- questions 16%
- docs 5%
- other 26%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →