Ecosystem · JavaScript · npm, Yarn, pnpm
Vulnerabilities in your npm dependencies, before they reach production.
LibWatch reads package.json and your npm, Yarn or pnpm lockfile, checks every package and tracks the end of life of your Node.js version.
What LibWatch reads in the repository
package.jsonpackage-lock.jsonyarn.lockpnpm-lock.yaml.nvmrc
Language version: .nvmrc, .node-version or .tool-versions
Nothing else: no cloning, no code run.
What LibWatch checks
The packages, and the Node.js version
npm packages
Known vulnerabilities
Every package in the lockfile checked against OSV, which includes GitHub advisories.
Node.js version
End of life
The declared version is tracked: you know when it stops getting fixes.
Health
License policy
Licenses that conflict with your project's policy are flagged.
An alert, in practice
An npm vulnerability, with the version that fixes it
Transitive dependencies count too: the lockfile shows everything.
Real severity
CVSS severity and presence in the CISA KEV catalog
What to do
The fixed version, and the affected project
Where
Email, Slack, Zulip or webhook, set per project
shop-frontend · Next.js
Example · analysis from October 22
-
End of life
Node.js (declared)
.nvmrc: 20
-
High severity
next
14.2.3
-
Up to date
axios
1.7.4
Rechecked every night at 2 a.m.
End of life
Where your Node.js version stands
Official nodejs.org schedule, checked on October 22, 2026.
| Version | Status | End of life | Action |
|---|---|---|---|
| Node.js 24 | Active LTS | → April 30, 2028 | Recommended version |
| Node.js 22 | Maintenance | → April 30, 2027 | Plan the upgrade |
| Node.js 20 | End of life | Since April 30, 2026 | Upgrade now |
Dates checked on October 22, 2026.
Get started
Your first report in a few minutes
No pipeline to change.
Connect GitHub or GitLab
Self-hosted GitLab instances included.
Choose your JavaScript repositories
LibWatch finds the files listed above on its own, even in a monorepo.
Read the report, set up alerts
Exploited vulnerabilities first, fixed versions, language end of life.
Frequently asked questions
LibWatch and JavaScript
Do I need to install anything in the project?
No. LibWatch reads dependency files through the GitHub or GitLab API, without adding anything to your pipeline.
Are private registries supported?
Yes. A package from a private registry is identified as such: its name is never sent to a third-party service, and it stays in the project's inventory.
Does LibWatch detect the version installed on the server?
No. LibWatch reads the version declared in the repository (version file, lockfile or manifest). It has no access to your servers.