Unified security scanning — SAST, containers, IaC, secrets, dependencies, and DAST from a single CLI.
Install
pip install argus-security
Quick Start
argus init # Create argus.yml config
argus scan # Run all configured scanners
Or scan immediately without a config file:
argus scan bandit gitleaks osv --severity-threshold high
Features
- 14+ security scanners -- SAST, secrets, containers, IaC, dependencies, DAST, supply chain, malware
- Single CLI --
argus scanruns everything, locally or in CI - Flexible selection -- run all scanners, specific ones, or groups
- Multiple output formats -- terminal, Markdown, SARIF, JSON
- Severity thresholds -- fail builds on
low,medium,high, orcritical - Docker-backed execution -- scanners run in containers when not installed locally
- Config-driven --
argus.ymlfor repeatable scan profiles - GitHub Actions integration -- composite actions for native CI/CD workflows
- Linting built in -- YAML, JSON, Python, JavaScript, Dockerfile, Terraform
Supported Scanners
| Category | Scanners |
|---|---|
| SAST | Bandit, OpenGrep, CodeQL |
| Secrets | Gitleaks |
| Containers | Trivy, Grype, Syft |
| IaC | Trivy IaC, Checkov |
| Dependencies | OSV Scanner |
| Supply Chain | zizmor + actionlint |
| Malware | ClamAV |
| DAST | ZAP |
| Compliance | FedRAMP SCN Detector |
Configuration
# argus.yml
scanners:
- gitleaks
- bandit
- osv
- trivy-iac
scan_path: "."
severity_threshold: high
MCP Server (AI Integration)
Argus includes an MCP server so AI assistants (Claude, Copilot, Cursor) can run scans, validate configs, and detect project characteristics directly.
pip install argus-security[mcp]
Add to your AI tool's MCP configuration:
{
"mcpServers": {
"argus": {"command": "argus", "args": ["mcp"]}
}
}
Available tools: argus_scan, argus_detect, argus_validate, argus_list_scanners, argus_init
Documentation
- Full docs: huntridge-labs.github.io/argus
- GitHub: github.com/huntridge-labs/argus
- Configuration reference: docs/config-reference.md
- Scanner reference: docs/scanners.md
- Examples: examples/
- Contributing: CONTRIBUTING.md
License
AGPL-3.0 -- see LICENSE.md for details.
Metadata
Release files for argus-security 1.12.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| argus_security-1.12.3.tar.gz | 578.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| argus_security-1.12.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / argus_security-1.12.3.tar.gz
| Download URL | argus_security-1.12.3.tar.gz |
|---|---|
| Size | 578.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c6ebf205648411371dc21ab6e22e67db72abf97e48d65e6813b4da7122760a9c
|
|
BLAKE2b-256 checksum How to use checksums |
53ad88c2e7d0a84777df670a26c88da255dd4a13fb4347ff4eb7f2731e89c84f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency logRelease files / argus_security-1.12.3-py3-none-any.whl
| Download URL | argus_security-1.12.3-py3-none-any.whl |
|---|---|
| Size | 660.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b9e4684eff61d70bf6df3571079788c400f7a032e934c119e353b5905132872
|
|
BLAKE2b-256 checksum How to use checksums |
c89b273d5779c14072eb621607c85c003004c317977ac7330421dda60fa1445d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency log