Function-level reachability vulnerability scanner for Elixir, Erlang and Gleam: OSV.dev and EEF CNA advisories checked against post-macro .beam call graphs (govulncheck for the BEAM).
# VulnCheck
[](https://hex.pm/packages/vulncheck)
[](https://hexdocs.pm/vulncheck)
[](https://github.com/Voskan/vulncheck/actions)
[](https://github.com/Voskan/vulncheck/blob/main/LICENSE)
[](#design-highlights)
**Function-level reachability vulnerability scanner for Elixir, Erlang, and Gleam (`govulncheck` for the BEAM).**
`vulncheck` bridges the gap between lockfile dependency scanners (`mix deps.audit`, `mix hex.audit`) and what your compiled BEAM release actually executes. Instead of failing CI whenever any transitive Hex package receives a CVE, `vulncheck` pairs **OSV.dev** and **Erlang Ecosystem Foundation (EEF) CNA CVE 5.1 `programRoutines`** metadata with **post-macro `.beam` bytecode call graphs, OTP supervision roots, Plug/Phoenix pipelines, and runtime adapter configurations** to prove whether vulnerable functions are reachable in your production code.

---
## Why VulnCheck Exists
Recent Hex ecosystem disclosures include dozens of structured CVEs across core packages such as `plug`, `phoenix`, `bandit`, `ash`, `mint`, `hackney`, `cowlib`, and `tesla`.
Traditional lockfile scanners suffer from two structural limitations:
1. **Package-Level Alert Fatigue:** Tools that only compare `mix.lock` versions flag an entire dependency even when the CVE affects a single optional parser, unused HTTP adapter, aggregate helper, or an older OTP runtime.
2. **Unused Official Symbol Data:** EEF CNA CVE 5.1 advisories explicitly publish affected MFA symbols under `programRoutines` (for example, <code>'Elixir.Plug.Conn.Query':decode/4</code> or <code>'Elixir.Ash.Action