Know what’s vulnerable before it’s exploited.
Pinhaul watches your Python and Java apps and your Docker containers around the clock — mapping every dependency to live CVE, exploit and EPSS data, and telling you exactly what to patch first.
Free during beta · No credit card · Invite-only onboarding
My Overview
Projects
Findings
Alerts
My Overview
- Projects
- 3
- Open findings
- 12
- Outdated deps
- 27
- Agents online
- 2
1 known-exploited (KEV) · 2 likely-exploited (EPSS ≥ 0.5)
Run pinhaul findings to see what needs patching first.
-
CVE-2021-44228 · log4j-core 2.14.1
via botocore → transitive · depth 3
KEV fix 2.17.1 -
CVE-2024-37891 · urllib3 2.0.7
python · requests ecosystem
EPSS 0.94 fix 2.2.2 -
GHSA-9wx4-h78v-vm56 · pillow 10.2.0
image parsing · container web-frontend
high fix 10.3.0
Built entirely on free, open security data
Google OSV
CISA KEV
FIRST EPSS
Exploit-DB
deps.dev
endoflife.date
Debian tracker
OpenSSF
GitHub GHSA
Trivy
Get started
From zero to full stack visibility in minutes
One command for your runtime, one container for your Docker host. Pinhaul keeps watching after you close the terminal.
- Install the SDK
-
pinhaul initcaptures your exact runtime inventory — Python and Java, direct and transitive — then streams only names and versions. - Deploy the agent
-
One
docker runand the agent inventories every container on the host, scans images with Trivy, and accepts on-demand scans from the console. - Fix what matters
-
Findings are ranked by what’s actually being exploited — CISA KEV first, then EPSS probability — with the exact fixed version for each. No 400-CVE wall of noise.
Chat with your stack
Two commands to your first finding
No forms, no scanners to configure, no CI to wire up. If you can install a package, you can know your exposure.
- Under a minute.
- The SDK fingerprints your runtime in the background and reports before your dev server finishes booting.
- Always current.
- Snapshots refresh on every deploy and engines re-sweep daily — yesterday’s clean report doesn’t lie to you today.
$ pip install pinhaul-0.7.1-py3-none-any.whl
$ pinhaul init
✓ 214 packages discovered · 61 transitive · python 3.12
✓ snapshot sent · 3 open findings
$ pinhaul findings
KEV CVE-2021-44228 · log4j-core 2.14.1 → 2.17.1
0.94 CVE-2024-37891 · urllib3 2.0.7 → 2.2.2
$ docker run -d -v /var/run/docker.sock:/var/run/docker.sock \
pinhaul-agent
✓ agent online · 4 containers · image scan queued
Reachability — our flagship engine
It doesn’t just list CVEs. It watches which ones your app actually runs.
Roughly 90% of CVEs in any stack sit in code that never executes. Every other scanner stops at “it’s installed.” Pinhaul’s SDK instruments the running process with sys.monitoring and records which packages’ functions your app truly calls — then tags each finding REACHED or present, never observed.
Near-zero overhead, pure stdlib, nothing leaves your process except counters. Static reachability tools guess from your source code at enterprise prices — this is ground truth from production, with pip install ergonomics.
How a finding reads
CVE-2024-37891 · urllib3 2.0.7 reached
urllib3.connectionpool.urlopen · 41,203 calls · 12m ago
CVE-2023-50447 · pillow 10.2.0 present
never observed executing — patch when convenient
Your 400-finding wall becomes: these 6 are live in production.
Detection engines
A dozen engines. Open data. Zero noise.
Every engine runs for every project, every night — and re-checks your inventory the moment a snapshot lands.
OSV sweep
freeEvery Google OSV advisory for your Python, npm and Maven packages, re-checked nightly and on every deploy — full records, not just IDs.
GHSA mirror
freeA local mirror of GitHub’s advisory database, so new pip/Maven advisories reach you without API rate limits — and often before our OSV query sees them.
CISA KEV
freeThe catalog of vulnerabilities with confirmed in-the-wild exploitation, synced twice daily. If one of your pins lands here, it jumps the queue.
EPSS ranking
freeFIRST’s exploitation-probability scores, refreshed daily — the difference between “patch this week” and “patch eventually” across 400 findings.
Exploit-DB mapping
free27,000+ public exploits indexed by CVE and joined to your findings — an “exploit available” chip with a link, slotted between KEV and EPSS.
Fix-radar
premiumWatches the upstream repos behind your pins for security-shaped commits — catches fixes days before any advisory exists, with the exact commit linked.
Backport radar
freeYour deb pin is “unpatched” upstream — but Debian shipped 1.19.8-1+deb12u2 yesterday. Our dpkg comparator catches distro backports other scanners miss.
Malware shield
freeThe OpenSSF malicious-packages feed, matched against your direct pins — a known-malware dependency is the loudest alert a security tool can fire.
Image & secret scanning
premiumTrivy scans every container image on your hosts — CVEs and leaked secrets — re-scanning when advisories change, not just when containers restart.
Log monitoring
premiumThe agent tails every container’s logs for security patterns — redacted before anything leaves your host.
EOL watch
freeYour Python runtime itself is a dependency. endoflife.date powers alerts when the interpreter you run in production passes end-of-life.
Dependency intelligence
freedeps.dev powers version freshness, license visibility and OpenSSF Scorecard maintenance signals — with the import-chain graph to explain how it all got in.
The data behind it
Free, open feeds — correlated, not just collected
Any scanner can subscribe to these. Pinhaul cross-references all of them against your live inventory and against each other — and our managed intel pipeline means we move before the feeds do.
- Google OSV
- The open vulnerability database — advisories for every major ecosystem, queried and mirrored.
- CISA KEV
- Confirmed in-the-wild exploitation. Twice-daily sync.
- FIRST EPSS
- Exploitation probability for every CVE, scored daily.
- Exploit-DB
- Public exploit archive, indexed by CVE nightly.
- Debian security tracker
- Distro backports that never change the upstream version number.
- OpenSSF malicious-packages
- Known-malware packages across every registry.
- GitHub advisory DB
- GHSA advisories, mirrored git-native with zero rate limits.
- deps.dev
- Exact resolved dependency graphs, licenses, Scorecard signals.
- endoflife.date
- Runtime end-of-life dates for the interpreter itself.
Security without the enterprise tax
Everything above runs on data that is free and open. You pay for the watching, not the feeds.
- 12
- detection engines
- ~60s
- to first inventory
- 2
- ecosystems — Python & Java
- $0
- cost of vulnerability data
Frequently asked questions
-
No. The SDK sends package names and versions — never your code, secrets, or environment variables. Even your hostname stays home: it’s hashed into a pseudonymous machine id on your machine, and that one-way hash is all we ever see. The agent reads container metadata and image layers on your own host and sends only what it finds: images, packages, vulnerabilities, and redacted log patterns.
-
Snapshots fingerprint your inventory and skip anything that hasn’t changed — client-side and again server-side. Most runs never leave your machine, and the ones that do are a small JSON payload.
-
Google OSV for advisories, CISA’s KEV catalog for active exploitation, FIRST’s EPSS for probability, deps.dev for version freshness, endoflife.date for runtime EOL, and Aqua’s Trivy for container images. All free and open — refreshed daily.
-
Most supply-chain attacks are fixed upstream days or weeks before an advisory is published. Fix-radar watches the repositories behind your pinned dependencies for security-shaped commits and flags them — with the fix version — even when no CVE exists yet.
-
During the beta, everything is free for waitlist members — including premium engines like fix-radar. When we introduce tiers, the core engines stay free and beta builders keep what they joined with. Join the waitlist to get your invite.
-
The parts that touch your machines run there, and they ship as source you can read: the agent is a small build context you
docker buildon your own host, the SDK a Python wheel, each with a published sha256 and every dependency pinned. The Pinhaul backend is hosted by us.
Your stack is already running. Start watching it.
One pip install, one docker run, and you’ll know exactly what’s exposed — before someone else finds it for you.