Integrate Whispers with Vulnesis. Scan source code and configuration files for hardcoded secrets including AWS keys, API tokens, passwords, and private keys with minimal false positives.
Install & scan
$ # Recommended - run without global install uv run --with whispers whispers --version # Install globally pip install whispers $ # Basic scan with JSON output uv run --with whispers whispers . --output whispers.json # Include static code analysis uv run --with whispers whispers . -a --output whispers.json
Run Whispers in CI
Scan on every push and upload the report as a workflow artifact:
- name: Scan for hardcoded secrets
run: |
pip install whispers
whispers . -a --output whispers.json
- name: Upload to Vulnesis
run: vulnetix upload --file whispers.json
How Vulnesis compares: better together
Vulnesis does not replace Whispers. Keep running it. Vulnesis sits on top of Whispers (and every other scanner you already own) turning disconnected tool outputs into one prioritised, fixable queue.
Whispers is strongest at its core category and also carries features in SAST, just as Vulnesis spans categories.
| Capability | Vulnesis | Whispers |
|---|---|---|
| Security coverage | ||
| SAST (static code analysis) | ✓ Built-in rules + Semgrep augmentation | ~ Only via optional Semgrep integration to find secrets embedded in source code; not a general SAST engine |
| SCA / dependencies | ✓ 40+ ecosystems, transitive graph | ✗ |
| DAST (dynamic testing) | ~ Ingests DAST results; no native dynamic engine | ✗ |
| Container & image | ✓ Image CVEs, base image, Dockerfile | ✗ |
| IaC / misconfiguration | ✓ Terraform, k8s, CloudFormation | ✗ |
| Secret scanning | ✓ 1,000+ rules, source + binary + git history | ✓ Core: detects passwords, API tokens, cloud/private keys, hashed creds, webhooks in structured config + code (CWE-798) |
| Cloud / CSPM | ✓ Cloud-posture findings, compliance tab | ✗ |
| Mobile (MAST) | ~ Ingests mobile scanner output; no native mobile engine | ✗ |
| License compliance | ✓ SPDX, copyleft/AGPL/SSPL policy | ✗ |
| SBOM generation | ✓ CycloneDX 1.7 + SPDX 2.3, cosign-signable | ✗ |
| Malware / supply-chain | ✓ De-duplicated corpus + install-time firewall (25 registries) | ✗ |
| Network / infra vuln | ~ Ingests network scanner output; no native network scanner | ✗ |
| Fuzzing | ✗ Ingests fuzzing crashes; no native fuzzer | ✗ |
| Pentest / bug bounty | ✗ Ingests pentest/bug-bounty findings; not a testing service | ✗ |
| The Vulnesis orchestration layer | ||
| Cross-scanner dedup & one queue (ASPM) | ✓ Correlates every scanner into one prioritised queue with ownership routing | ✗ |
| Exploit-intel prioritisation | ✓ EPSS, CISA KEV, Coalition ESS, CWSS, Vulnesis LEV | ✗ |
| Reachability analysis | ✓ Tree-sitter + CVEAffected; direct/transitive/semantic | ✗ |
| Versioned VEX + audit trail | ✓ Immutable OpenVEX/CycloneDX, cosign-signable | ✗ |
| Safe Harbour autofix | ✓ Resolves + applies the nearest safe version | ✗ |
| End-of-life policy | ✓ Flags/blocks past-EOL runtimes & packages | ✗ |
| SSVC / risk-based policy | ✓ SSVC v2 + CISA/FedRAMP/Essential-8 presets | ✗ |
✓ full · ~ partial · ✗ not covered
What Whispers does well
- Purpose-built for structured config files (YAML, JSON, XML, INI, .env) where secrets are most often committed by accident, parsing key-value pairs via a plugin architecture rather than blind regex over raw text
- Low false-positive design: 21 curated built-in rules organized by group and severity (Info to Critical), with granular allow/deny filtering by path glob, key/value regex, rule ID/group and severity
- Highly configurable with custom inline rules and a pluggable parser model; runs as both a standalone binary and an importable Python module for pipelines
- Optional Semgrep integration extends detection into static code across Python, PHP, Java/Scala/Kotlin, JS/TS and Go for embedded credentials
Where Vulnesis adds to it: Vulnesis runs its own secret detection (AWS keys, GitHub PATs, Slack/Stripe tokens, high-entropy strings) but treats a specialist like Whispers as a complementary ingest source: it consolidates Whispers findings into the cross-scanner deduplicated queue, adds exploit-intel prioritisation, versioned VEX and Safe Harbour autofix that Whispers itself does not provide.
No migration, no rip-and-replace. Whispers keeps doing what it does best; Vulnesis adds the orchestration, exploit-intelligence prioritisation and remediation layer built for the way AppSec works today. Software Factory agents on a Pix Sandbox can then turn the findings from any scanner into pull requests that a person approves. How Software Factory works.
Centralise Whispers results in Vulnesis
Upload Whispers JSON output to the Vulnesis platform to deduplicate findings, prioritise them with EPSS, CISA KEV and Coalition ESS exploit intelligence, and track remediation across every scanner in a single queue.