Ravage
Ravage is an evidence-first web security research agent for controlled,
authorized targets. This package provides the ravage CLI and runtime modules.
The project is a pre-1.0 research alpha. Use it only on local fixtures, isolated labs, or systems you own and are explicitly authorized to assess. The active public CLI is localhost-first.
Source Checkout
The canonical development setup is the repository bootstrap:
scripts/bootstrap.sh
source .venv/bin/activate
ravage --version
The 0.0.1 PyPI package is a legacy preview. Until a newer tagged release is
published, use a source checkout and record its exact commit when reporting
results.
Active Commands
Run deterministic probes without model calls:
ravage scan brief.yaml --run-dir runs/local-scan --report
Run the model-driven agent after configuring a model route and adding a useful
context.description to the brief:
ravage attack brief.yaml \
--model-profile hosted-openai \
--model-tier low \
--allow-paid-models \
--report
Inspect and verify a run:
ravage observe runs/<run-dir>
ravage audit verify runs/<run-dir>
ravage report runs/<run-dir> --brief brief.yaml
Use ravage --help and each subcommand's --help for the installed version.
External scanners such as nmap, sqlmap, katana, nuclei, and ffuf are
not Python dependencies. From a source checkout, use
scripts/install_tools.sh --method docker --execute, then run
ravage tools check.
The optional browser extra adds Playwright support; install its Chromium
runtime separately with playwright install chromium.
Documentation
See the repository README, setup guide, and operator guide.
Ravage is open source under the Apache License 2.0. See the repository
SECURITY.md, CONTRIBUTING.md, DISCLAIMER.md, and LICENSE before use or
contribution.
Metadata
Release files for ravage 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ravage-0.5.0.tar.gz | 552.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ravage-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / ravage-0.5.0.tar.gz
| Download URL | ravage-0.5.0.tar.gz |
|---|---|
| Size | 552.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
262e0057f97555cd29c2eeb41b70cf0117f89d52dd1d092f66973b6c7cb05bbb
|
|
BLAKE2b-256 checksum How to use checksums |
d596090a9c9a228bca2aedc4d7b0e84d3431469b5cc72f3bee41e7c21f0b9fc1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 14, 2026.
Transparency logRelease files / ravage-0.5.0-py3-none-any.whl
| Download URL | ravage-0.5.0-py3-none-any.whl |
|---|---|
| Size | 683.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
371bb914565097a90ae7652b5e47b6ece1740c9528d15ddad456bd06ab7a0aeb
|
|
BLAKE2b-256 checksum How to use checksums |
122cc6618cfaf65d8e03e81aeec85c60c7241971f98f10d23b971e56859575e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 14, 2026.
Transparency logSecurity for ravage 0.5.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ravage-0.5.0.tar.gz
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 Jul 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.