Maze dependency findings sorted by severity, from a Critical Apache Commons Text RCE down to Low.

Prioritize and fix exploitable dependencies


Trusted by the fastest growing security teams

Contentful
Zipline
Alloy
Halcyon
Cohere
Forge
PartsSource

Maze marks an ejs template injection not exploitable, since the vulnerable option is never exposed to attacker input.

Exploitable, not reachable


Maze traces a lodash prototype pollution from an SQS consumer message body into lodash.merge, marked exploitable.

Beyond traditional call graphs


Maze rates a PyYAML RCE exploitable but low likelihood, because its route sits inside a private EKS cluster.

Risk based on your context


Maze dependency findings in the Investigating state, with no severity assigned yet while Maze works through them.

Reasoning without frontier cost


Agents investigate every dependency

Agents find the manifest that pulled in each package, the exact version your build used, and the function that calls it, for direct and transitive dependencies alike.
Maze traces a golang-jwt vulnerability from the vulnerable dependency to a reachable refresh route.
Maze traces a golang-jwt vulnerability from the vulnerable dependency to a reachable refresh route.

Find and fix
exploitable dependencies

Frequently Asked Questions

Talk to us about how Maze’s agents
investigate your dependencies.

Maze AI SCA finds every vulnerability in your open-source dependencies, direct and transitive, and investigates each one the way your best security engineer would. Agents trace each package to the code that calls it and prove whether it’s exploitable in your environment, and the ones that are come with evidence and a fix.

Most SCA tools use rules to find vulnerabilities and then rank them by CVE score. Some add reachability on top. Maze goes a step further, with agents checking whether an attacker can control what reaches the vulnerable code in your application, so you only fix what’s exploitable.

Reachability tells you the vulnerable code can be called, not whether an attacker can trigger the flaw. In one investigation, a vulnerable library was reachable five different ways, but every request it made went to a fixed internal service, so an attacker had no way to send it a malicious payload. Instead of another urgent ticket, that finding came off the list with the evidence to show why.

Yes. Maze Code scans for vulnerable dependencies (SCA), flaws in your own code (SAST), secrets, licenses, and more, so you don’t need a separate scanner to get started.

Yes. Agents trace the full call path through your code and every open-source package in between.

Because Maze uses AI to find and investigate vulnerabilities instead of static rules, it isn’t limited to the languages a rule set was written for. That includes older languages like C++.

Yes. Maze investigates the packages every pull request adds and blocks merges on real risk. Unlike other solutions, pull requests get the same agents and the same investigation, without adding time. Fixes route to the developer who owns the code or to the coding agents your team already uses.

We aim to keep pricing simple and fair and offer an annual contract. Large language models aren’t cheap, but we’ve worked hard to optimize cost and performance to make sure our pricing is reasonable.

Yes, Maze is cloud-hosted in AWS. Customers can choose between multi-tenant and single-tenant hosting.

Maze has been built for enterprise from day one. We’re ISO 27001 and SOC 2 Type II certified.



Autonomous security
from commit to production



Resources