Essential
Active
Technical operation, security, session, consent, and basic interface preferences.
Daily development, security review and technical evidence. Code Security and Flow cover different moments in your work.
Find risks in your editor and CI. Share context, compare scans and prepare the next change.
Local scanning, dependencies and context inside VS Code-compatible editors.
Open guideFilters, shared suppressions and optional AI triage, off by default.
Open guideUnderstand where each analysis runs and what context connected and AI features use.
Open guideHistory, scan comparisons, shared false positives and project reports.
Open guideInvestigate an application in the lab, check findings and prepare reviewable fixes and evidence.
Original-source investigation, executable checks and outcomes that distinguish certainty from uncertainty.
Open guideCriteria before patching, isolated candidates and a GitHub delivery with evidence and remaining work.
Open guideSelected requirements, partial coverage and traceability between results, fixes and reference frameworks.
Open guideChoose by the work you need to do. Both products can be part of the same process.
| What you need | ||
|---|---|---|
| When to use it | During development and in GitHub Actions or Azure Pipelines. | An investigation of an authorized commit and scope. |
| Analysis scope | Code, packages, secrets, configuration and AI/MCP security rules. | Fifteen coordinated tools with a lab, investigation and verification. |
| What supports the result | Static rules, intrafile flows and OSV vulnerability advisories. | Executable methods and independent verification; confirmed, refuted or insufficient-evidence outcomes. |
| How changes are prepared | AI-assisted explanations and proposals according to plan. The user chooses what to apply. | Verified fixes when criteria are met and reviewable pull requests. The team decides the merge. |
| What the team shares | History, scan comparisons, suppressions and PDF/CSV exports. | Evidence by phase, blockers, remaining work and application order for fixes. |
| Availability | Extension, CI integrations and dashboard. | In development; early access according to project and configuration. |
Let's discuss your repository, team and the evidence you need.