Meerkat

Security early warning

Know before the CVE.

Meerkat watches vendor pre-announcements, security mailing lists, government CERTs and trusted researchers — and emails you the moment something affects the packages and products you use, including the warnings that come before a CVE exists.

Start freeAdd a badge to your repo

No access to your code needed. Public repos are read from their lockfiles; private projects can upload a lockfile or SBOM.

Real example · PHP2Shell, October 2026 (UTC)
  1. 20 Oct 16:39 A security researcher posts about two critical PHP flaws
  2. 20 Oct 20:22 Warning reaches the oss-security mailing list
  3. 20 Oct 20:32 PHP publishes an advance notice of a critical security release
  4. 21 Oct 13:48 CVE records published — most tools start here
  5. 26 Oct Listed as actively exploited

The first public warnings came about 21 hours before the CVE records. That is the window Meerkat is built for.

How it works

1 · Tell us what you run

Add GitHub repositories — we read lockfiles, manifests, Dockerfiles and GitHub Actions automatically — or pick products and packages to watch.

2 · We watch, continuously

Vendor security channels, project announce lists, CERT alerts, trusted researchers, CVE, OSV and GitHub advisories, Linux distributions and fixed patch days.

3 · One thread per issue

You get one email thread that updates as an issue moves from early warning to vendor notice, advisory and exploitation. Lower-priority updates go to a daily digest.

Every alert says how sure we are

Unconfirmed report

A trusted researcher or several independent sources report a serious problem. No fix may exist yet — you get time to prepare.

Vendor pre-notice

The vendor announces an upcoming security release, or a fixed patch day is coming. Book the maintenance window now.

Advisory published

Details and fixed versions are out. We tell you which of your projects use an affected version.

Actively exploited

Attackers are using it. Patch or mitigate immediately.

What Meerkat covers

Open-source packages

npm, PyPI, Maven, Go, Rust, RubyGems, Packagist, NuGet, Pub, Hex, Swift, Docker base images and GitHub Actions — plus Debian, Ubuntu, Red Hat, SUSE, Alpine, Amazon Linux and more.

Products and platforms

Microsoft, Apple, Google, Cisco, Fortinet, Palo Alto Networks, Ivanti, Citrix, VMware, Oracle, SAP, Atlassian, Siemens, Kubernetes, WordPress and hundreds more products by name.

Show it on your repo

Add the Meerkat badge to your README. It shows how many packages Meerkat watches for that repository, and lets visitors subscribe to early warnings for it.

Get your badge

Meerkat: 1,284 packages MeerkatMeerkat 1,284 packages1,284 packages

Questions

Do you need access to my code?

No. For public GitHub repositories we only read dependency files (lockfiles, manifests, Dockerfiles, workflow files). For private projects, upload a lockfile or a CycloneDX/SPDX SBOM.

Will I get flooded with email?

No. Each issue is one email thread, updated only when its status changes. You choose the minimum level for instant email; the rest arrives in one daily digest.

Where does the information come from?

Only public sources — vendors, open-source projects, CERTs, advisory databases and public posts. Every alert links to the original sources.

Can an early warning be wrong?

Early reports can be incomplete, so they are clearly labelled “Unconfirmed”. Critical unconfirmed reports from social media are checked by a person before they are sent.