Automatic discovery
Connect once and Leavory maps projects, repositories, and pipelines on its own, in the background.
Leavory turns the scan results from your Azure DevOps, GitHub, and GitLab pipelines into a short list of what to fix today.
Connects to
Built on
Cross-references
Leavory replaces tracking spreadsheets and scattered alerts. A single place where risk, context, and recommendation live together.
Each capability below shares the same context, so a finding moves from detection to the right fix without changing tools.
Connect once and Leavory maps projects, repositories, and pipelines on its own, in the background.
A plain-language read on whether it’s exploitable in practice and what to change first.
Continuous updates make sure no new CVE slips by unnoticed in your code.
Vulnerability intelligence, impact analysis across every project, and AI-drafted remediation, in one view. CISA KEV flags active exploitation. EPSS adds exploitation probability.
See how it worksFix first
Ranked by active exploitation and exploitation probability
| Finding | Severity | Status |
|---|---|---|
| JWT token without expirationauth-service | Critical | New |
| Secret in environment variablepayments-api | Critical | AI analyzed |
| AWS access key committedinfra-terraform | Secret | AI analyzed |
| SQL injection in /ordersmobile-gateway | High | New |
| Dependency with unpatched CVEcheckout-web | High | New |
| Missing security header (CSP)billing-service | Medium | AI analyzed |
JWT token without expiration
Why it matters
Tokens issued by this service never expire. If one leaks, it stays valid indefinitely and can be replayed against the API.
What to change first
exp claim when tokens are
issued.
Example findings
See the risk across your whole organization. Leavory maps every project, repository, and pipeline, and a ready-made Azure Pipelines template scans each build. Only the results reach Leavory. Your code stays in Azure DevOps.
Projects, repositories, and pipelines are discovered in the hierarchy you already use. Nothing to recreate or tag by hand.
A ready-to-use template runs Trivy and publishes the SBOM and scan artifacts. No agents to install.
Every project, repository, and pipeline links straight back to where your team already works.
Also on GitHub or GitLab? They connect the same way and land in the same view, which helps mid-migration or after an acquisition.
Platform
Every project, repository, and pipeline mapped on its own, from the dashboard down to the images running in production.
Know in one screen whether you are safer than last week.
Every project mapped on its own, with DORA metrics per team.
Open a repository and see what is failing, with health scores per team.
Every pipeline found in the hierarchy you already use, scanned with Trivy.
The images running in production, next to the projects and pipelines behind them.
Stop triaging thousands of CVEs. See only what hits your packages and is being exploited, and where a new CVE lands the moment it drops.
Open your repository, see what is failing, and get the fix drafted down to the dependency and version to change.
Every project, repository, and pipeline mapped on its own, with DORA metrics and health scores per team.
Know in one screen whether you are safer than last week, with an executive summary and evidence ready for the next audit.
Four steps, built on Trivy, the industry-standard scanner. The scanning stays in your pipeline; the intelligence starts here.
Authorize your Azure DevOps organization in a few clicks, no agents to install. GitHub and GitLab connect the same way.
Leavory runs Trivy in your pipeline. Never used Trivy? We hand you a ready-to-use Azure Pipelines template (or GitHub Actions and GitLab CI) that generates the SBOM and scan artifacts.
Every component is correlated against OSV, NVD, GitHub Advisories, CVE.org, CISA KEV, and EPSS using the SBOM and artifact metadata, no source code involved.
Findings ranked by active exploitation (CISA KEV) and exploitation probability (EPSS), with exactly what to change: dependency, version, and manifest.
Trivy, SAST, Sonar, and secret scanning run inside your own pipeline. Leavory only collects their results, SBOM, and scan artifacts. In SaaS, it never touches your repositories at all.
Tell us which platform you use, and an engineer, not a sales bot, will reach out to schedule a demo.