HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vigil-agency
vigil
JavaScript2026–2026
vigil-agency / vigil

vigil

The Security Agency That Never Sleeps — AI-powered security operations platform

2Distinct people
5Mentions
0Explicit recommenders
18GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Security Agency That Never Sleeps — AI-powered security operations platform

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval5 dated mentions

Observed mentions: 2026-03-09 13:45:14 UTC to 2026-03-16 14:13:03 UTC.

0122026-03-09 12:00:00 UTC to 2026-03-09 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 9, 12:002026-03-09 18:00:00 UTC to 2026-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 00:00:00 UTC to 2026-03-10 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 06:00:00 UTC to 2026-03-10 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 12:00:00 UTC to 2026-03-10 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-10 18:00:00 UTC to 2026-03-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-11 00:00:00 UTC to 2026-03-11 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-11 06:00:00 UTC to 2026-03-11 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-11 12:00:00 UTC to 2026-03-11 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-11 18:00:00 UTC to 2026-03-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-12 00:00:00 UTC to 2026-03-12 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-12 06:00:00 UTC to 2026-03-12 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-12 12:00:00 UTC to 2026-03-12 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-12 18:00:00 UTC to 2026-03-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-13 00:00:00 UTC to 2026-03-13 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 13, 00:002026-03-13 06:00:00 UTC to 2026-03-13 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-13 12:00:00 UTC to 2026-03-13 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-13 18:00:00 UTC to 2026-03-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-14 00:00:00 UTC to 2026-03-14 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-14 06:00:00 UTC to 2026-03-14 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-14 12:00:00 UTC to 2026-03-14 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-14 18:00:00 UTC to 2026-03-15 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-03-15 00:00:00 UTC to 2026-03-15 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-15 06:00:00 UTC to 2026-03-15 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-15 12:00:00 UTC to 2026-03-15 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-15 18:00:00 UTC to 2026-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-16 00:00:00 UTC to 2026-03-16 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-16 06:00:00 UTC to 2026-03-16 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-16 12:00:00 UTC to 2026-03-16 18:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsMar 16, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 9, 12:002026-03-09 12:00:00 UTC2026-03-09 18:00:00 UTC110
Mar 9, 18:002026-03-09 18:00:00 UTC2026-03-10 00:00:00 UTC000
Mar 10, 00:002026-03-10 00:00:00 UTC2026-03-10 06:00:00 UTC000
Mar 10, 06:002026-03-10 06:00:00 UTC2026-03-10 12:00:00 UTC000
Mar 10, 12:002026-03-10 12:00:00 UTC2026-03-10 18:00:00 UTC000
Mar 10, 18:002026-03-10 18:00:00 UTC2026-03-11 00:00:00 UTC000
Mar 11, 00:002026-03-11 00:00:00 UTC2026-03-11 06:00:00 UTC000
Mar 11, 06:002026-03-11 06:00:00 UTC2026-03-11 12:00:00 UTC000
Mar 11, 12:002026-03-11 12:00:00 UTC2026-03-11 18:00:00 UTC000
Mar 11, 18:002026-03-11 18:00:00 UTC2026-03-12 00:00:00 UTC000
Mar 12, 00:002026-03-12 00:00:00 UTC2026-03-12 06:00:00 UTC000
Mar 12, 06:002026-03-12 06:00:00 UTC2026-03-12 12:00:00 UTC000
Mar 12, 12:002026-03-12 12:00:00 UTC2026-03-12 18:00:00 UTC000
Mar 12, 18:002026-03-12 18:00:00 UTC2026-03-13 00:00:00 UTC000
Mar 13, 00:002026-03-13 00:00:00 UTC2026-03-13 06:00:00 UTC000
Mar 13, 06:002026-03-13 06:00:00 UTC2026-03-13 12:00:00 UTC000
Mar 13, 12:002026-03-13 12:00:00 UTC2026-03-13 18:00:00 UTC000
Mar 13, 18:002026-03-13 18:00:00 UTC2026-03-14 00:00:00 UTC000
Mar 14, 00:002026-03-14 00:00:00 UTC2026-03-14 06:00:00 UTC000
Mar 14, 06:002026-03-14 06:00:00 UTC2026-03-14 12:00:00 UTC000
Mar 14, 12:002026-03-14 12:00:00 UTC2026-03-14 18:00:00 UTC000
Mar 14, 18:002026-03-14 18:00:00 UTC2026-03-15 00:00:00 UTC211
Mar 15, 00:002026-03-15 00:00:00 UTC2026-03-15 06:00:00 UTC000
Mar 15, 06:002026-03-15 06:00:00 UTC2026-03-15 12:00:00 UTC000
Mar 15, 12:002026-03-15 12:00:00 UTC2026-03-15 18:00:00 UTC000
Mar 15, 18:002026-03-15 18:00:00 UTC2026-03-16 00:00:00 UTC000
Mar 16, 00:002026-03-16 00:00:00 UTC2026-03-16 06:00:00 UTC000
Mar 16, 06:002026-03-16 06:00:00 UTC2026-03-16 12:00:00 UTC000
Mar 16, 12:002026-03-16 12:00:00 UTC2026-03-16 18:00:00 UTC211

What Hacker News says

5 sources
Vigil is an open-source security operations platform. The v1.1 release adds an embedded security knowledge engine with 356 pre-built entries that answer in <1ms without calling an LLM. What's in the brain: - 85 MITRE ATT&CK techniques (all 14 tactics, real CVEs, detection/mitigation) - 89 port-to-service mappings with known vulns (21 through 50000) - 48 NIST controls (CSF 2.0 + 800-53 Rev 5) - 40 CompTIA Security+ domains - 30 cross-framework compliance maps (PCI DSS 4.0, HIPAA, SOC 2, ISO 27001, CIS v8) - 27 remediation templates with language-specific fixes - 17 CVE patterns, 10 OWASP Top 10 Web, 10 OWASP LLM Top 10 Ask "T1059" or "port 445" — instant structured answer with detections, mitigations, CWE mappings. No LLM round-trip. When reasoning IS needed, the brain enriches the prompt with your security profile, section context, recall
Read the rest
ed memories, and relevant KB hits before sending to your AI provider. Also new in v1.1: - DAG workflow automation (chain agents, conditions, HTTP calls into security pipelines) - 28 AI security agents with editor (autonomous pentester, forensics, red team, compliance) - Smart provider routing (Ollama local, Claude API, Codex — per-agent selection, fallback chains) - Kali Linux bridge container with 11 tools (nmap, nuclei, nikto, sqlmap, etc.) - Docker Compose stack: Vigil + PostgreSQL + Ollama + Kali bridge Runs air-gapped with Ollama. Zero data leaves your machine. Express.js + vanilla JS, 6 npm dependencies. GitHub: https://github.com/vigil-agency/vigil CHANGELOG: https://github.com/vigil-agency/vigil/blob/main/CHANGELOG.md reply
In Vigil v1.1 – Open-source security ops platform with embedded AI brain
Vigil is an open-source security operations platform. The v1.1 release adds an embedded security knowledge engine with 356 pre-built entries that answer in <1ms without calling an LLM. What's in the brain: - 85 MITRE ATT&CK techniques (all 14 tactics, real CVEs, detection/mitigation) - 89 port-to-service mappings with known vulns (21 through 50000) - 48 NIST controls (CSF 2.0 + 800-53 Rev 5) - 40 CompTIA Security+ domains - 30 cross-framework compliance maps (PCI DSS 4.0, HIPAA, SOC 2, ISO 27001, CIS v8) - 27 remediation templates with language-specific fixes - 17 CVE patterns, 10 OWASP Top 10 Web, 10 OWASP LLM Top 10 Ask "T1059" or "port 445" — instant structured answer with detections, mitigations, CWE mappings. No LLM round-trip. When reasoning IS needed, the brain enriches the prompt with your security profile, section c
Read the rest
ontext, recalled memories, and relevant KB hits before sending to your AI provider. Also new in v1.1: - DAG workflow automation (chain agents, conditions, HTTP calls into security pipelines) - 28 AI security agents with editor (autonomous pentester, forensics, red team, compliance) - Smart provider routing (Ollama local, Claude API, Codex — per-agent selection, fallback chains) - Kali Linux bridge container with 11 tools (nmap, nuclei, nikto, sqlmap, etc.) - Docker Compose stack: Vigil + PostgreSQL + Ollama + Kali bridge Runs air-gapped with Ollama. Zero data leaves your machine. Express.js + vanilla JS, 6 npm dependencies. GitHub: https://github.com/vigil-agency/vigil CHANGELOG: https://github.com/vigil-agency/vigil/blob/main/CHANGELOG.md
In Vigil v1.1 – Open-source security ops platform with embedded AI brain

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.