Public metrics
Everything on this page is measured from the live estate and refreshed nightly by an automated GitHub-API and SOC snapshot. Numbers are re-measured, never carried forward. Built 2026-10-20T01:07:26Z.
Repositories — the nine public artifacts
Live counts from the GitHub API at build time. Releases are the tagged, dated ones (v0.1.0 of the four flagship landed 2026-10-19).
| Repository | Stars | Forks | Releases | Topics | Last push |
|---|---|---|---|---|---|
| dmrobbi/agentic-aicustom agentic AI system specifically designed for smaller LLMs | 0 | 0 | 0 | 7 | 2026-10-15 |
| dmrobbi/kevstigKEV x STIG coverage checker: how many known-exploited CVEs touch the platforms we maintain DISA STIG baselines | 0 | 0 | 1 v0.1.0 | 8 | 2026-10-19 |
| dmrobbi/laya-controlLaya control plane for the agentic SOC — serve, shadow evals + 300-gate, GPU power control, loopback→docker-br | 0 | 0 | 0 | 6 | 2026-10-12 |
| dmrobbi/luks-container-guideLUKS2 container vault: verified host setup + Docker / Podman / Kubernetes guides (open-while-running, locked-a | 0 | 0 | 0 | 8 | 2026-10-12 |
| dmrobbi/md-docsMarkdown doc library addon for the SOC dashboard — Node stdlib only, optional bearer gate, mounts as /docs on | 0 | 0 | 0 | 6 | 2026-10-18 |
| dmrobbi/soc-disk-healthSMART physical-disk health monitoring addon for an OpenClaw/Wazuh SOC: smartd + wazuh rules + nightly JSONL pr | 0 | 0 | 0 | 6 | 2026-10-14 |
| dmrobbi/soc-openclawRunning a full SOC with OpenClaw: AI analysts on a single-node Wazuh stack | 0 | 0 | 1 v0.1.0 | 8 | 2026-10-19 |
| dmrobbi/stig-baselinesDISA STIG baseline checklists (CKL) generated from official DISA XCCDF sources — STIG Viewer 2.x/3.x ready | 2 | 0 | 1 v0.1.0 | 8 | 2026-10-19 |
| dmrobbi/wazuh-stackSingle-node Wazuh docker stack for the agentic SOC — compose, cert tooling, integrations; secrets env-injected | 0 | 0 | 1 v0.1.0 | 8 | 2026-10-19 |
Stars and forks over time
One row per snapshot day since tracking began (2026-10-20). The sparkline is drawn from this page's own snapshot history; the raw, full dataset is at /metrics/data.json.
Methodology
- GitHub stars/forks/releases/topics — GitHub REST API for the nine public repos, measured from this host's authenticated runner at build time; rate window and token owned by the automation, no manual counts.
- Alerts and vulnerability findings — document counts from the estate's own indexer indices (wazuh-alerts-*, wazuh-states-vulnerabilities-*), read at build time. Never alert content: only the count.
- Device enrollment — the manager API's enrolled total (the stable subscribed-estate figure, not the drifting active count).
- CKLs generated / STIG platforms — re-counted from the stig-baselines repository tree (checklist files generated from vendor XCCDF; platform directories in the baseline estate).
- Tickets — the remediation ticket ledger (created / closed / open) rebuilt from the SOC ticket store; counts only, no ticket bodies.
- Health checks — the hourly SOC health suite's latest result line ("N ok, M failed"), as measured in the journal at build time.
- Median alert decision — the live decision log (laya_gated_decision kind, ok rows, own durations): the median in milliseconds.
- Refresh cadence — nightly isolated snapshot job (05:04 UTC), owner-gated deploys to this page. JSON snapshot: data.json.
What this does not track
No alert content, hostnames, internal IPs, or customer data — the public layer is counts and release facts only. No traffic analytics, no follower counts, no sponsor totals until those exist to be honest about. The ops dashboard itself stays LAN-only; what reaches this page is the scrubbed, numeric shadow of it.