Local analysis. Structured reports.
Audit Sherpa
Find the engineering risks hiding across Flutter and Dart repositories without sending source code to the dashboard.
Why teams use it
Turn local tool output into a reviewable risk story.
Tool provenance
See which Technical Debt, Dependencies, Architecture, and Release Discipline reports contributed to an audit.
Actionable findings
Filter and group findings or recommendations by source, repository, priority, category, and status.
Trust boundary
Source code stays local by design; generated reports may include project metadata and evidence fields.
Workflow
Generate locally. Upload reports. Review in the dashboard.
- Run Sherpa tools from a local environment or CI.
- Package an audit bundle with branch, commit, metadata, and tool reports.
- Open dashboard drill-downs for reports, findings, recommendations, and evidence.