- CMMC Level 2 contractors and subcontractors managing software supply chain risk
- Teams that need audit-ready evidence without a SaaS dependency or cloud uploads
- Organizations where dependency files cannot leave the local network
- Contractors building POA&M documentation for a C3PAO assessment
Three commands to your first scan.
docker pull swynnjr/risksnap
mkdir -p ~/risksnap-data
docker run --rm -v ~/risksnap-data:/data swynnjr/risksnap \
scan /data/requirements.txt --output-dir /data
Windows (PowerShell): use an absolute path, e.g. -v C:\Users\you\risksnap-data:/data
- PDF evidence pack with full traceability
- CSV with scored findings
- Scan history tracked locally across projects
- Native scanning for Python (requirements.txt) and Node.js (package-lock.json) · SBOM scanning via CycloneDX and SPDX for any ecosystem
- Audit-grade PDF evidence packs
- Scan history across multiple projects
- POA&M item visibility
- CSV export of findings and POA&M data
- Web interface (Streamlit) and command-line modes
- Runs entirely locally — your dependency files never leave your network
- White-label PDFs with your organization's branding
- Software asset inventory — CMMC CM.L2-3.4.1 evidence (CSV + PDF)
- Delta reports — audit-grade remediation evidence over time
- POA&M sync from scans
- POA&M editing (CLI and web UI)
- CSV import/export round-trip for team collaboration
- POA&M PDF generation in conventional CMMC format
Found a bug or need help? Contact us →
Audit-ready outputs from every scan.
Upload a dependency manifest. RiskSnap scans against OSV and CISA KEV and produces a scored risk summary — no account, no external upload.
Licensed POA&M workflow: sync findings, assign owners, edit remediation plans, generate audit-ready PDFs. All data stays local.
Full feature set available via command line for automation and CI integration.
Dated, traceable evidence pack with full vulnerability scoring metadata. Supports CMMC Level 2 RA.L2-3.11.2 documentation.
POA&M summary table with stable POAM IDs, status, severity, and target dates — conventional CMMC POA&M format.
Per-POA&M detail: control references, weakness description, remediation plan, responsible party, and closure tracking.
Your files stay on your machine.
- All processing happens inside the Docker container on your machine
- Dependency files are never uploaded to any external server
- One optional network call: license validation — only when a license key is provided, cached 24 hours locally
- Security contact: security@wynn-systems.com
docker pull swynnjr/risksnap works with just Docker installed on your machine — no sign-in required for the free tier.requirements.txt) and Node.js (package-lock.json). Via SBOM: any ecosystem your CycloneDX or SPDX SBOM describes — including Java/Maven, Go, Rust, and more. Bring a pre-generated SBOM from tools like the CycloneDX Maven plugin or Syft.