Evaluate Oryon alongside GitLab

1. 01

   Analysis starts on your machine.

   Local SAST, code, dependencies and configuration in your editor workflow. You control connected features and AI assistance, according to your plan.

2. 02

   From the editor to every delivery.

   The engine ships with the extension. Connect code analysis, dependencies and CI integrations with your team's platform in one workflow.

3. 03

   One review the whole team can reuse.

   Shared suppressions, history, scan comparisons, CSV exports and PDF reports. Detection becomes ongoing work your team can track.

Capabilities, side by side.

The table describes documented features; it does not measure performance or detection quality. Commercial features may depend on product, plan and configuration.

What you need	Code Security	GitLab
Editor integration	✓Documented Scan as you edit or save, or start a file or repository scan; configure profiles and exclusions.	+Optional / plan dependent VS Code findings require Ultimate; active-file SAST is remote and experimental. ↗
Static code analysis	✓Documented Static analysis of code, secrets, infrastructure, pipelines and AI/MCP security. Combines patterns with data tracking within each file. Profiles and exclusions adapt the scan to the repository.	✓Documented Basic SAST; Advanced SAST with Ultimate. ↗
Dependencies	✓Documented Extends the inventory of packages and their relationships from the repository, including Maven projects. Automatically attempted in the extension and CI; native analyzers provide a fallback when it is unavailable.	+Optional / plan dependent Dependency Scanning requires Ultimate. ↗
Secrets	✓Documented Static analysis of code, secrets, infrastructure, pipelines and AI/MCP security. Combines patterns with data tracking within each file. Profiles and exclusions adapt the scan to the repository.	✓Documented Pattern-based Secret Detection; generic detection depends on tier and release status. ↗
CI integration	✓Documented Run the same analysis core from GitHub Actions and Azure Pipelines, with OIDC and a project token.	✓Documented Analyzers run in GitLab CI/CD. ↗
AI-assisted fixes	+Optional / plan dependent Explains causes, risk and impact and proposes changes, diffs, effort and verification checks. Available according to plan and configuration; the user reviews and applies the proposal in the editor.	+Optional / plan dependent AI vulnerability resolution for Ultimate and eligible configurations. ↗
SAST without SaaS code upload	✓Documented OpenGrep bundled with the extension; local SAST works offline once the engine is extracted. AI and sync use the network.	✓Documented Self-managed GitLab and runners; IDE SAST does send the file to the server. ↗
Infrastructure & configuration	✓Documented Rules for Terraform, Docker, Kubernetes, CI/CD and configuration; coverage depends on format and rule.	✓Documented KICS in CI; dashboards and approval workflows depend on tier. ↗
Profiles & exclusions	✓Documented production_security/full profiles, path inclusion and exclusion, and .gitignore support.	✓Documented Scope variables and exclusions; advanced ruleset customization depends on tier. ↗
Selective MDN compatibility	✓Documented Selective MDN assessment: String.replaceAll against configured browsers. Other warnings require validation; this is not a general browser compatibility audit.	—Not documented in this scope No MDN compatibility assessment documented in the reviewed scope. ↗
Shared triage decisions	✓Documented Project-level shared false-positive suppressions, with restoration from the extension and dashboard.	+Optional / plan dependent Shared vulnerability management in Ultimate. ↗
History & reporting	✓Documented History, comparisons, audit PDF and JSON/CSV exports. The advanced AI report depends on the plan.	✓Documented SAST JSON artifacts; history and consolidated dashboard with Ultimate. ↗

Product scope