Reachability-aware

Security thatknows yourcodebase.

Reachability-aware scanning built into the same plugin. It tells you whether a vulnerable package is actually on a path your code runs — not just that it exists.

Request access See reachability

Reachability model

Reachable beats present

Most tools flag every advisory in your lockfile. Jericho separates vulnerabilities that exist from vulnerabilities your code can actually reach.

reachable: false[email protected] → tree-shaken, never imported

Noise most scanners report

A flawed package is in your tree, but no code path in your application ever calls the affected function. Real, but not exploitable here.

reachable: true[email protected] → app/http/client.py:84

What Jericho surfaces first

The vulnerable function sits on a call path your code executes. This is the finding that deserves your attention now.

Scanning layers

What Jericho scans

Four scanning layers, built into the same plugin as debugging.

01/dependency exposure

Dependency exposure

Maps every package and version against known advisories across your dependency tree.

02/secret detection

Secret detection

Flags credentials, tokens, and keys committed anywhere in your source.

03/reachability heuristics

Reachability heuristics

Decides whether vulnerable code sits on a path your application actually executes.

04/evidence-bound findings

Evidence-bound findings

Every finding cites the exact file, line, and call path it was derived from.

Live proof

Watch it trace a vulnerability

Find what actually reaches you.

Request access and scan your codebase for vulnerabilities that matter.

Request access