Current coverage is already broad.
Passive URL scanning, SEO/AEO/readiness, scanner coverage metadata, GitHub alert path, API keys, MCP, monitoring, and threat ingestion are represented.
Comparison
Competitor-grade coverage, LaunchLock safety gates.
LaunchLock is being built toward broad scanner coverage while keeping original implementation, honest report limits, and owner-gated active checks.
Parity roadmap
Passive scan
Reports
MCP
Deep scan
Report signals
CurrentPassive scanner breadth
NextCustomer consent UI
GuardrailActive scans gated
Current
Passive scanner breadth
Next
Customer consent UI
Guardrail
Active scans gated
Report UX is part of parity.
The product direction prioritizes grouped fixes, evidence clarity, scanner run metadata, and prompt handoff over raw finding volume.
Active scanning stays controlled.
Verified ownership, consent, scope management, rate limits, and audit logs stay required before customer-facing active checks expand.