High signal
Architecture drift
Boundaries blur until feature code, shared code, and infrastructure become hard to reason about.
arch_sherpa Engineering Risk Cartography
Map engineering risk before it becomes delivery drag.
Flutter Sherpa Suite turns architecture, dependencies, release discipline, and technical debt into measurable signals for Flutter and Dart teams.
01 / Diagnostics
Flutter projects rarely fail all at once.
They slow down through small, repeated compromises: unclear boundaries, risky dependencies, inconsistent releases, undocumented debt, and code health debates based on opinions instead of evidence.
Elevated
Dependency risk
Dependencies can be current, popular, or internal and still introduce ecosystem, maintenance, coupling, or platform-readiness risk.
dep_sherpa Watch
Release friction
Version intent, changelog detail, and actual release behavior drift out of alignment.
semver_sherpa Concentrated
Invisible technical debt
Known pain stays scattered across comments, tickets, and memory instead of reviewable signals.
techdebt_sherpa 02 / Suite
One suite. Four engineering lenses.
Each Sherpa tool studies a different route through the codebase, then emits signals a team can review, track, and act on.
Release discipline
semver_sherpa
Keep versions, changelogs, and release intent aligned.
$ semver_sherpa check
$ semver_sherpa release --type minor Signal Release checkpoint consistency Open on pub.dev
Architecture control
arch_sherpa
Detect boundary erosion before it becomes a refactor nobody wants to start.
$ arch_sherpa analyze --config sherpa.yaml Signal Boundary violation trend Open on pub.dev
Dependency intelligence
dep_sherpa
Surface dependency, coupling, ecosystem, and platform-readiness risks.
$ dep_sherpa scan --format json Signal Platform-readiness exposure Open on pub.dev
Technical debt visibility
techdebt_sherpa
Turn scattered debt into visible, reviewable, prioritised engineering signals.
$ techdebt_sherpa report --output markdown Signal Debt hotspot priority Open on pub.dev
Install
Install one signal. Measure one risk.
Choose the Sherpa tool that matches the risk you want to make visible first.
Dart CLI package · pub.dev
semver_sherpa
Keep version intent, changelog entries, and release checkpoints aligned.
dart pub global activate semver_sherpa 03 / Signals
From opinions to signals.
Before
- This module feels messy.
- Dependencies are probably fine.
- We should release soon.
- We know there is debt somewhere.
After
- Architecture rule violations increased 18%.
- Dependency risk is concentrated in a small set of direct and transitive packages.
- Changelog and version intent are inconsistent.
- Debt hotspots are concentrated in three features.
04 / Workflow
Designed for engineering workflows, not vanity dashboards.
Sherpa signals are meant to live where engineering decisions already happen: local terminals, CI checks, reviews, and reports.
- 01 Analyze
- 02 Report
- 03 Review
- 04 Act
- 05 Track
- Local CLI usage
- CI integration
- Machine-readable JSON
- Human-readable Markdown
- Reviewable engineering signals
05 / Teams
Built for teams that care about maintainability.
- Senior Flutter engineers
- Tech leads
- Staff / principal engineers
- Architecture-minded teams
- Teams scaling from one app to many
- Teams that want objective engineering quality signals
06 / FAQ
Questions engineering teams ask first.
It is designed primarily for Flutter and Dart projects, with a strong focus on architecture, dependencies, release discipline, and maintainability.
No. It complements linters and static analysis by focusing on engineering workflow signals, architectural boundaries, dependency risk, release discipline, and technical debt visibility.
The tools should be designed to work locally and in CI, producing both human-readable and machine-readable outputs.
Start with the package that matches the most visible risk: releases, architecture boundaries, dependencies, or technical debt. Each tool is designed to produce a focused signal before a broader process is introduced.