Prevent Risks Before Code Is Committed
Overview
The Heeler CLI allows organizations to scan for security risks directly in the development workflow via a pre-commit hook, so before code is pushed, merged, or deployed. Developers can use the pre-commit hook independent of the Heeler Application and without manually downloading and installing the Heeler CLI.
By integrating Heeler into local development and CI pipelines, teams can:
Detect secrets before they are committed
Prevent accidental credential leaks
Enforce security guardrails at commit time
Reduce remediation cost and cycle time
Improve compliance posture (SOC 2, ISO, etc.)
Version 1.0.3 includes support for secret scanning plus dependency vulnerability and SBOM workflows for Go and Java (Maven). Heeler will expand the CLI functionality to include other languages, packages (licenses, sca), SAST, and exports in future releases.
Repository
The Heeler CLI repository is located here https://github.com/Heeler-Security/heelercli with detailed instructions and examples.
Add this code to your .pre-commit-config.yaml for the auto-installing version of the pre-commit hook.
repos:
- repo: https://github.com/Heeler-Security/heelercli
rev: 1.0.0 # replace with desired release tag
hooks:
- id: heelercli-autoSecrets Options
The Heeler CLI inspects staged diffs, common formats, and validates where possible to reduce false positives. The CLI has options to customize its use for your environment, specifically:
which support use cases like
Scan the repo but exclude build output and vendor code:
Fail the scan only for specific secret types:
Show only validated findings:
Vulnerabilities Options
The CLI has options to customize its use for your environment, specifically:
which support use cases like
Fail on critical/high only:
Identify new issues:
Output
The output of the Version 1.0.3 pre-commit hook looks like:
When a secret is detected, the check will block the commit while showing the its value, type, and file location for validation. In case of a false positive or other requirement, developers can still force the commit using git's --no-verify flag.
When one or more vulnerabilities are detected, it will show a summary of findings including title, package, advisory status, and URL. The check will not block the commit unless the CLI is configured to do so, e.g., by setting the CLI to fail for critical/high vulnerabilities (see example). Even so, developers can still force the commit using git's --no-verify flag.
Last updated
Was this helpful?
