Hole Monitor

Security holes, sent to your agents as they appear.

Hole Monitor watches seven vulnerability sources and POSTs a signed OSV record to your webhook when an advisory that matches your filters is published or changes. It is an API first, built for receivers that are AI agents or code that hands the event to one.

Free plan: 100 tracked terms, 3 endpoints, signed webhooks. No card.

Example delivery, structured content (values illustrative)
POST /hooks/hole-monitor
webhook-id: dlv_01jd…
webhook-timestamp: 1763700000
webhook-signature: v1,K5o…=

{
  "schema_version": "1.9.2",
  "id": "CVE-2026-12345",
  "aliases": ["GHSA-xxxx-xxxx-xxxx"],
  "modified": "2026-11-21T14:05:12Z",
  "affected": [{
    "package": { "ecosystem": "npm", "name": "example-lib" },
    "ranges": [{ "type": "SEMVER",
      "events": [{ "introduced": "0" }, { "fixed": "4.2.1" }] }]
  }],
  "severity": [{ "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/…" }],
  "database_specific": {
    "max_base_score": 9.8,
    "kev": { "date_added": "2026-11-21" },
    "epss": { "score": 0.41, "percentile": 0.97 },
    "content": "structured",
    "event": { "type": "kev_added", "changed": ["kev"] }
  }
}

Sources

Merged into one record per advisory, keyed by CVE ID where one exists.

  • CVE List
  • NVD
  • GitHub Advisory Database
  • Drupal security advisories
  • CISA KEV
  • Wordfence Intelligence
  • EPSS

Time from upstream publication to first delivery attempt: about 5 minutes for GitHub advisories, up to about 12 for the CVE List, 15 for Drupal, about an hour for KEV, 2 hours for NVD. Wordfence records arrive when Wordfence sends them. Details.

How it works

  1. Create a key and an endpointFrom the dashboard, the REST API or the MCP server. The endpoint proves it wants the traffic by echoing a verification code.
  2. Add filtersPackages (npm, PyPI, Packagist, WordPress plugins…), vendors, products, minimum CVSS, minimum EPSS, KEV only, Drupal risk.
  3. Receive signed eventspublished, updated, kev_added and withdrawn, signed per Standard Webhooks and retried for about 3 days.
  4. Let your agent actOpen a pull request, bump a version, page a person. The receiver templates start a GitHub Actions run from a delivery.

Built for programs, not inboxes

OSV payload

Every delivery is an OSV 1.9.2 record with scores, KEV, EPSS and Drupal risk under database_specific. A JSON Schema is published.

Prose left out by default

Advisory text is written by third parties and can carry instructions aimed at a model. Structured content sends IDs, versions, packages and numbers only. How.

Standard Webhooks

HMAC-SHA256 signatures, a stable webhook-id for deduplication, secret rotation with a 24-hour overlap, and a delivery log you can page through.

API, OpenAPI, MCP

Every action is a REST call described in OpenAPI 3.1. The MCP server exposes the same routes as tools.

Filters as code

PUT /v1/endpoints/{id}/filters replaces an endpoint's filter set in one call, so filters can live in your repository.

Nothing dropped silently

Deliveries over the daily limit are deferred and sent after midnight UTC, oldest first. Failed deliveries can be redelivered.

Set up with your agent

Create an API key in the dashboard, put it in HOLE_MONITOR_API_KEY, then paste this into your coding agent.

For agents: /llms.txt, /llms-full.txt, MCP at https://api.holemonitor.live/mcp.

Pricing

Metered by tracked terms: each vendor, product or package value in your filters. Every plan gets signed webhooks, all sources, all event types and the full API.

Free

$0

  • 100 tracked terms
  • 3 endpoints
  • 1 broad filter
  • 5,000 deliveries a day
  • 14-day delivery log
Start free

Business

$149 / month

  • 10,000 tracked terms
  • 200 endpoints
  • 50 broad filters
  • 250,000 deliveries a day
  • 90-day delivery log
Choose Business

Full comparison and yearly prices.

Questions

Is this real time?
Within minutes. Most sources are polled at the fastest rate they allow; only Wordfence pushes. The figures above are the expected delays.
Do I get advisories published before I signed up?
No. The service is forward-only: it starts from its launch and does not backfill history.
Does it match my exact versions?
No. Filters match a package, vendor or product at any version. Each record carries affected ranges and fixed versions so your receiver can decide.
Email or Slack?
No. Webhooks are the only channel that carries advisories. Account notices, such as a disabled endpoint, come by email.
Where does the data come from, and under what terms?
Each record names its sources and the notices their terms require. See attribution.