Roadmap

What is already live, what is actively being built, and what is on deck next. Priorities can shift as the product evolves.

Shipped

Available now.

MCP support for Claude Code, Cursor, and Windsurf

Run crawwwl audits directly from MCP-compatible coding tools without leaving your editor.

GitHub repository audits

Audit public GitHub repositories by URL, without cloning them locally first.

Dashboard with audit history and report viewing

Browse past audits, open full reports, review score changes, and track token usage from the dashboard.

Usage-based billing

Pay only for the AI usage consumed during paid audits, with token count and estimated cost shown after each run.

In progress

Actively being worked on.

More accurate scoring

Improve how penalties are weighted, avoid zeroed-out scores, and handle non-applicable categories more cleanly.

Cleaner issue grouping

Group repeated findings, collapse long file lists, and reduce noise in larger audits.

Fewer false positives for React and Next.js

Make the scanners more context-aware around hooks, server components, dynamic imports, and common framework patterns.

Planned

Next priorities once current work lands.

VS Code extension

Run audits from the editor and review findings alongside the code you are working on.

GitHub Actions integration

Run crawwwl in pull requests and post a summary of findings and score changes automatically.

Fix suggestions in CLI output

Show concise fix suggestions next to common findings directly in terminal output.

Score history in the dashboard

Track overall and per-category trends over time, and compare audit runs side by side.

Ask crawwwl AI about your audit

Ask follow-up questions inside an audit report and get answers grounded in that audit's code context.

Ideas

Worth exploring, but not committed.

Skills system

Optional packages for domain-specific checks, starting with areas where teams want more tailored auditing.

Framework expansion

Support for Vue, Svelte, and Astro once React and Next.js coverage is where it needs to be.

Team accounts

Shared usage balance, team-level audit history, and organization-wide settings.

CI/CD reporting

Structured output for pipelines, with better severity-based exits, artifacts, and reporting integrations.