Feature · Nightly watch

Spotted before you, even on projects nobody touches.

A dependency that was safe at your last deployment can become critical six months later. Every night, LibWatch re-checks the inventory of all your projects against new vulnerabilities, without re-reading your repositories.

Turn on the watch

Read with an AI .md version

One night

What happens while you sleep

2 a.m.

The watch starts

Every project is scheduled, spread across the night so the sources aren't overloaded.

During the night

Each inventory is re-checked

OSV (GitHub advisories included), CERT-FR for PHP, EPSS, KEV and end-of-life schedules.

As soon as a vulnerability affects you

The alert goes out

By email, Slack, Zulip or webhook, depending on your settings.

Monday, 9 a.m.

The weekly digest

The vulnerabilities of the past seven days, project by project.

Analysis and watch

Two complementary mechanisms

On every push or scheduled

An analysis

— Re-reads the repository's dependency files.

— Updates the inventory.

— Uses one analysis from your plan.

Every night

The nightly watch

— Doesn't re-read the repository.

— Re-checks the known inventory against new vulnerabilities.

— Uses no analyses.

Is the watch included during the trial?

Yes. During the 14-day trial, you get every feature of the plan you chose, nightly watch included.

What if a project hasn't been analyzed for a long time?

The watch covers projects analyzed in the last 90 days. Beyond that, run a new analysis to bring the inventory up to date: the watch picks it up again the following night.

Can I choose the time?

No. The watch starts every night at 2 a.m. Paris time and is spread over two hours. Scheduled analyses, on the other hand, are set project by project: daily, weekly or monthly.

Tonight, your projects will be checked again.