Supported Versions
| Version | Supported |
|---|---|
| 1.0.x | :white_check_mark: |
Security Guarantees and Trust Boundaries
vulncheck separates scanning from building so teams can choose the trust boundary that matches their CI environment:
- Zero Runtime Dependencies:
vulncheckrelies exclusively on Elixir and Erlang/OTP standard library modules (:beam_lib,:digraph,:ets,:httpc,:ssl,:public_key,:crypto,:zip,JSON). - Strict TLS Verification: All advisory feed downloads enforce TLS peer verification (
verify: :verify_peer) against system root CAs (:public_key.cacerts_get/0) with hostname verification enabled. - Static Inspection of Target Artifacts (Prebuilt Mode): When scanning prebuilt artifacts (
compile: falsein the GitHub Action orvulncheck/mix vulncheckon an existing_build/),vulncheckinspects lockfiles (mix.lock,rebar.lock,manifest.toml),.appresource terms, and compiled.beamchunks (:abstract_code,:imports,:exports,:attributes) without executing target dependency code. - Trusted Build Mode (
compile: true): Enabling compilation (compile: truein the GitHub Action or runningmix compile/rebar3 compile/gleam buildbefore scanning) executes the target project's build tools, macros, and Mix/rebar3 compilers. Usecompile: trueonly on trusted checkouts. For untrusted pull requests (such as forks), do not grantsecurity-events: writeor repository secrets to a job that compiles untrusted code: either run the build/scan in an unprivileged workflow and upload SARIF from a separateworkflow_runjob, or scan prebuilt artifacts withcompile: false. - Resource Limits and Cache Isolation:
.beamanalysis enforces per-file size limits (64 MiB), workspace.beamfile count limits (20,000 files), and per-file worker timeouts (15 s), reporting any truncated or failed module as incomplete analysis. On-disk.beamsummary caches are separated from advisory feed caches (feeds/vsbeam-v4/), bounded in size, decoded with[:safe], and validated against theModuleSummaryschema before reuse; CI workflows should cache onlyfeeds/. - Atom Table Invariant: External JSON feeds and lockfiles never call
String.to_atom/1. Warm scans that read validated.beamsummaries add zero atoms. Cold.beamanalysis reads module chunks via:beam_lib.chunks/2, which internalizes atoms present in those.beamchunk tables without loading or executing the modules. - Soundness Over Silence: Dynamic dispatch (
apply/3with unresolved targets) and active OTP supervision daemons are classified conservatively asPOTENTIALLY_REACHABLErather than silently suppressed.
Reporting a Vulnerability
Please do not report security vulnerabilities—especially reachability false negatives, TLS bypasses, or archive extraction issues—through public GitHub issues.
Report vulnerabilities privately via GitHub Security Advisories on github.com/Voskan/vulncheck or by emailing voskan1989@gmail.com with [SECURITY] vulncheck in the subject line.
You can expect an initial acknowledgement within 48 hours and a coordinated remediation timeline within 7 days.