Early warning system
of vulnerabilities
Meerkat reads 1,000+ sources around the clock and emails you when a security problem touches the packages and products you run — often hours or days before a CVE exists.
- no code access
- no JavaScript
- free for individuals
PHP2Shell, October 2026
Most tools wait for a CVE record before they say anything. By then this flaw had been public for almost a day. Meerkat's alerts start with the first credible warning, and follow the issue in one email thread.
Head start before the CVE: 21 h 09 min. All times UTC.
How it works
- 01
Tell it what you run.
Point it at a GitHub repository, upload a lockfile or SBOM, or pick products by name.
- 02
It keeps watch.
1,000+ sources, around the clock, matched against exactly the packages, versions and products you use.
- 03
You hear first.
One email thread per issue, escalating as it develops — from first warning to fix to exploitation.
Public GitHub repo
- Sign up.
- In Projects, add
owner/repo. - Meerkat reads the dependency files and emails you.
Private code
- Sign up and create a private project.
- Run one command with OSV-Scanner or Syft.
- Only package names and versions are sent.
An alert, as it arrives
From: Meerkat Alerts <alerts@meerkatsec.win> Subject: [UNCONFIRMED][CRITICAL] Two critical flaws reported in PHP Unconfirmed report · severity critical Two critical flaws reported in PHP Why you're getting this: • acme/api: uses PHP (affected version) • Watched product: PHP What to do now: This is an early, unconfirmed report. A fix may not exist yet. Check where you use it, plan an emergency update window, and watch this thread: we will update it when the vendor confirms. Timeline: • First public signal: 2026-10-20 16:39 UTC (before the CVE was published) • No CVE published yet Details: https://meerkatsec.win/app/alerts/…
Every alert says how sure we are
| Level | Name | Means | Do |
|---|---|---|---|
| ▲L2 | Unconfirmed report | Early reports of a serious problem, before any fix or CVE. | Prepare |
| ■L3 | Release announced | A security release is on its way. | Book a window |
| ●L4 | Advisory published | Fixed versions are out, matched to your projects. | Update |
| ✖L5 | Actively exploited | Attackers are using it now. | Patch now |
Coverage
Packages and platforms
npm · PyPI · Maven · Go · crates.io · RubyGems · Packagist · NuGet · Pub · Hex · Swift · Docker images · GitHub Actions · Debian · Ubuntu · Red Hat · SUSE · Alpine · Amazon Linux
Products, by name
Microsoft · Apple · Google · Cisco · Fortinet · Palo Alto Networks · Ivanti · Citrix · VMware · Oracle · SAP · Atlassian · Siemens · Kubernetes · WordPress · OpenSSL · PHP · nginx · Jenkins · GitLab · and hundreds more
A badge for your README
[](https://meerkatsec.win/r/github/acme/api)
Plans
| Individual | Teammost teams | Business | |
|---|---|---|---|
| Price | Freeno card needed | $5per month | $50per month |
| For | one developer | small teams | companies |
| Projects | 3 | 15 | 100 |
| Extra watched items | 25 | 150 | 1,000 |
| Users | 1 | 5 | 25 |
| Slack and webhooks | — | yes | yes |
| API | — | — | yes |
| Get started | Choose Team | Choose Business |
Notes
- Do you need access to my code?
- No. Public repositories are read through their dependency files; private projects upload a lockfile or SBOM.
- Will I get flooded with email?
- No. One thread per issue, updated only when its status changes. Everything else waits for the daily digest.
- Can an early warning be wrong?
- Yes, sometimes — which is why early reports are labelled “Unconfirmed” and critical ones are checked by a person.
- Is it really free?
- Yes. The Individual plan is free. Team and Business add projects, seats, Slack, webhooks and the API.
Be the first to know.
get started →