Watcher
v3.7.0 open-sourceThe section your link pointed to isn't on Watcher's page any more, so we've brought you to the top.
Django & React JS platform for automated cybersecurity threat detection, monitoring domains, data leaks, CVEs, and ransomware with AI-powered intelligence.
BULK_CREATE_MAX_ITEMS=500 BULK_ACTION_MAX_ITEMS=500 curl -s 'https://<watcher-host>/api/site_monitoring/alert/?site=42' -H 'Authorization: Token <your-api-token>' CERTSTREAM_VERSION=v1.8.2 SEARX_PATH=../Searx/searx HTTP_PROXY=http://proxy.corp.example.com:3128 HTTPS_PROXY=http://proxy.corp.example.com:3128 NO_PROXY=thehive.internal,misp.internal,smtp.internal OIDC_CREATE_USER=False LOGIN_MODE=both OIDC_RP_CLIENT_ID=<your_client_id> OIDC_RP_CLIENT_SECRET=<your_client_secret> curl -s https://<your-domain>/api/schema/ | jq .info.title docker compose run watcher bash -c 'python manage.py populate_db' curl -s 'https://watcher.example.com/api/data-leak/alerts?page=1&page_size=50' | jq '.data[]' curl -s 'https://watcher.example.com/api/dns-finder/dns_monitored?page=2&page_size=100' | jq '.data[]' docker compose run watcher bash python manage.py migrate python manage.py populate_db
Summary
Watcher is an open-source threat-intelligence platform, built on Django and React, that discovers and monitors emerging cybersecurity threats such as suspicious domains, data leaks, CVEs, and ransomware activity using AI-assisted analysis. It runs as a self-hosted service, deployable on a webserver or via Docker, and connects to external systems like TheHive, MISP, Slack, SearxNG, and CertStreamCertStreamA real-time feed of SSL/TLS certificates logged to Certificate Transparency logs, maintained by Calidog Security, giving cyber tools instant visibility into newly issued certificates for domain monitoring or phishing detection. through a dedicated connectors dashboard with health checks and encrypted credential storage. It suits CTICTICyber Threat Intelligence: structured knowledge about adversaries — their tactics, infrastructure, and indicators — that tools consume to prioritize detections or enrich alerts with context. and threat-hunting teams who need a central place to track indicators and manage response workflows, such as its approval queue for UDRP domain transfers, rather than a SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. alerting pipeline. It sits in the threat-intelligence and monitoring space alongside other CTI aggregation platforms, with a full timeline audit trail covering changes across modules. First committed in 2020, it remains active, with 16 contributors, 44 commits in the past year, and a release as recently as 30 days ago.
Django & React JS platform for automated cybersecurity threat detection, monitoring domains, data leaks, CVEs, and ransomware with AI-powered intelligence.
How Watcher helps
Which of my flagged UDRP cases actually had their domain transfer signed off by a human?
queues each 'won' case as a pending action for admin review instead of auto-transferring, and records approve or reject decisions against that case
Which of my external integrations have quietly stopped working?
a scheduled check tests every configured connector each Monday and raises a single pending-action alert per failure, without repeating it on subsequent failures
Are my connector credentials sitting in the database in plain text?
sensitive fields like passwords, tokens, and API keys are stored encrypted at rest, with existing values re-encrypted automatically when the schema is migrated
Can someone outside my organization log into Watcher just by authenticating through our SSO provider?
a setting restricts OIDC login to accounts an admin already created, turning off automatic account creation for unrecognized SSO users
Which connector is broken right now, and is it even configured?
the connectors dashboard reports each integration's live health as healthy, unhealthy, or not yet tested, separately from whether it is configured, incomplete, or disabled
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Watcher, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Watcher puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What Watcher connects to, runs on and detects, read from its release notes and docs. So far: 1 new detection.
1 change, tracked since Oct 1, 2026.
-
Oct 12026
new Subdomain Takeover (Dangling DNS) Detection
Covers 15: Amazon S3, Microsoft Azure Web App, GitHub Pages, Heroku, Netlify, Fastly and 9 more
their CNAME chain is resolved and matched against 15 known takeover-able provider fingerprints (Amazon S3, Microsoft Azure Web App, GitHub Pages, Heroku, Netlify, Fastly, Shopify, Zendesk, Bitbucket, Ghost, Help Scout Docs, Pantheon, Surge.sh, Tumblr, UserVoice), and confirmed via DNS (NXDOMAIN) or an HTTP signature probe.
Nothing first seen in this window. That doesn't mean Watcher shipped nothing, only that we found no record of it.
How we count
Read from 1 of 18 release notes and docs updates we hold for Watcher. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Watcher's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
18 entries
No entries match these filters.
- October 20263
- July 20261
- June 20261
- May 20261
- April 20261
- February 20261
- December 20252
- November 20251
- July 20252
- February 20251
- January 20251
- August 20241
- December 20211
- July 20211
Project health
Issue, contributor and maintainer activity in thalesgroup-cert/Watcher, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 3 −3 vs prior 12 months
- Maintainers 2 +1 joined · −0 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 116 days first maintainer reply 15 days
- Open backlog 8 of 76 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 8
- Contributors / month 3
- Commits / month 6
- Stars 1,382
- bugs 32%
- features 32%
- questions 5%
- other 31%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.