Security monitoring · dependencies, languages, WordPress
Vulnerabilities in your stack, seen first.
LibWatch monitors the dependencies in your GitHub and GitLab repositories, your language versions and your WordPress sites. It tells you when a vulnerability actually affects you, and what to fix first.
14-day trial, then from €39 excl. VAT per month · Hosted in France by OVHcloud
How it works
Three steps, then it runs on its own
No pipeline to change to get started: connecting your account is enough.
-
Connect your projects
GitHub, GitLab (self-managed included) or a WordPress site. Choose the repositories to monitor.
-
LibWatch builds the inventory
It reads your dependency files and language versions, and keeps only the list of packages and their versions.
-
You hear about it when it matters
Exploited vulnerabilities (KEV catalog) come first, then the most severe; alerts go out by email, Slack, Zulip or webhook.
What other scanners miss
More than a list of packages
-
End of life
Your language too
An up-to-date library running on PHP 8.1 or Ruby 3.0 is still exposed. LibWatch tracks support for your languages and frameworks.
End-of-life detection → -
CERT-FR
French security alerts
Advisories and alerts from ANSSI, the French cybersecurity agency, are built in for PHP: an affected PHP version is flagged by the following night at the latest.
Alert prioritization → -
One plan
Git and WordPress together
A repository or a WordPress site counts as one project. No separate tools for code and for sites.
For agencies and IT service providers → -
Every night
Even forgotten projects
The inventory is checked against new vulnerabilities every night, without using up an analysis.
Nightly watch → -
SBOM
CycloneDX and SPDX
Export a machine-readable bill of materials, validated against the official schemas.
SBOM export → -
MCP server
Queryable by your AI tools
Your AI assistants look up the vulnerabilities in your projects, and start an analysis if you allow it.
The MCP server →
Privacy
Your code stays with you
LibWatch reads your dependency files through the GitHub or GitLab API and keeps only the list of your packages and their versions. No repository is cloned, no code is executed.
What LibWatch keeps
- — The name and version of each package
- — The declared language versions
- — The vulnerabilities found and their history
What it does not do
- — Clone your repository: only dependency files are read, one at a time
LibWatch in numbers
-
14
package managers
From Composer to Pub, plus WordPress sites.
-
2 a.m.
nightly watch
Every night, all your projects checked again.
-
1 night
for CERT-FR alerts on PHP
A published alert is matched against your PHP versions at the next nightly check.
-
14 days
trial
On the plan of your choice. Nothing is charged before the trial ends.
Frequently asked questions
Before you connect your repositories
Does LibWatch read my code?
Do I need to change my CI pipeline?
Which ecosystems are covered?
What happens at the end of the 14-day trial?
Your first project is analyzed in minutes.
Connect a repository or a WordPress site. You will immediately see its vulnerabilities, its language versions and what needs fixing.
Hosted in France by OVHcloud