Specht is an open-source tool that collects reports from security scanners into one workspace.
Instead of dumping scanner alerts on developers, Specht shows what changed. Teams can set waivers for low-risk findings and keep builds green.
View the project on GitHub (minh-tg/specht) ↗
My role
Author & Lead Engineer
I started and maintain Specht as an open-source project:
- Built the Go backend and PostgreSQL schema.
- Built the CLI for developer workflows.
- Built the pipeline to map scanner outputs to a shared schema.
- Built the waiver engine for temporary exceptions in CI/CD.
- Built the Model Context Protocol (MCP) server for editor assistants.
Why I built this
The inspiration for Specht comes from my time at Accso in Germany, where I worked on vulnerability tooling that we open-sourced as accso/SecureCheckPlus. Specht takes those lessons and adapts them for CI/CD and AI assistants.
Modern software projects run multiple security scanners: static analysis, dependency audits, and secret scanning.
Each tool uses its own format and alert output. Teams end up with alert fatigue. Developers ignore warnings, or builds fail over minor issues that do not affect production.
I wanted a tool between scanners and CI/CD to handle triage and time-bounded waivers.
What it does
- Central inbox: Collects findings from code, dependency, and container scanners.
- Time-bounded waivers: Developers can set expiration dates (such as 14 days) on low-risk findings to keep work moving.
- CI/CD gates: Runs during pull requests to verify code against security rules.
- AI assistant bridge: Includes an MCP server so editor tools can query repository security status.
Project status
Specht is an open-source project licensed under AGPL-3.0. The Go backend, CLI, database schema, and MCP server are functional. A web dashboard is in development.