Install from GitHub Marketplace
Open the approved Marketplace listing, then choose all repositories or a selected set.
Static audits and draft autofix PRs for Python, FastAPI, GitHub Actions, and Docker repositories.
secrets/, .env, Terraform, auth, and security paths are excluded.
RepoWave keeps the loop short: Marketplace install in, GitHub webhook in, static analysis out, and a draft PR only for allow-listed changes.
Open the approved Marketplace listing, then choose all repositories or a selected set.
A signed webhook schedules a scan for that commit.
Findings include rule, severity, file, line, and message.
Only formatting and import-order fixes can create a PR.
Rules cover the parts of a Python service repo that commonly drift during normal development. RepoWave is intentionally narrower than broad SAST suites, and stronger at the conservative Python/FastAPI lane it claims.
Dead code, blocking calls in async code, missing HTTP timeouts, logging hygiene, and Pydantic compatibility.
Untyped returns, missing response models, and route handlers that do too much directly.
Unpinned actions, missing permission blocks, and unsafe workflow patterns.
Root containers, missing health checks, and common Dockerfile quality issues.
For teams that want a one-time repo cleanup plan before installing another recurring tool, RepoWave turns scan output into a short, prioritized engineering report and starts with a prefilled request email.
Include the repository URL, default branch, deadline, and primary concern when you reply so the audit can be scoped quickly.
Top Marketplace tools win by being easy to install, clear about pricing, and trustworthy about security. RepoWave matches that buying checklist while staying focused on auditable Python repository hygiene.
The allow-list lives in core/security/autofix_gate.py. Only formatting and import order categories produce PRs. Security, secrets, deployment, migration, CI permissions, Terraform, auth, and .env paths stay advisory.
You can read the entire safety boundary in the docs.
Buyers expect documentation, privacy, support, status, and pricing to be one click away. RepoWave keeps those surfaces explicit.
Repository source is fetched for analysis and deleted after the scan. Finding metadata is retained for 90 days.
Privacy policySupport runs through support@repowave.dev. Security reports use the SECURITY: subject prefix.
Install, scan behavior, autofix boundaries, uninstall, limits, and troubleshooting are documented in one place.
Read docsThe health endpoint is public and returns a minimal readiness response for uptime monitoring.
Health checkPublic repositories can scan for free. Paid plans are priced by private repository capacity so small Python teams do not have to buy a broad per-developer AppSec platform.
For public repositories that want continuous scanning without auto-remediation.
For one private Python service that needs safe GitHub-native hygiene.
For maintainers with a handful of private Python/FastAPI repositories.
For small teams with several private repositories under one GitHub organization.
For larger Python repo fleets that still want conservative automation.
No. RepoWave is not a broad AppSec suite. It is a narrow, conservative GitHub App for Python/FastAPI repository hygiene and safe mechanical autofix PRs.
No. Paid plans can open draft PRs, but RepoWave never self-merges and never edits denied paths like secrets, auth, Terraform, migrations, or .env.
Install from the approved Marketplace listing, pick repositories, then push. There is no YAML file, CI runner, or token rotation required.