skott vs Rev-dep
skott builds a dependency graph and detects circular dependencies, unused files, and unused third-party dependencies, with a graph explorer. rev-dep covers the same checks in one config and runs faster - but skott also visualizes the graph, which rev-dep does not.
At a glance​
| skott | Rev-dep | |
|---|---|---|
| Primary focus | graph analysis + visualization | dependency hygiene + architecture |
| Runtime | Node | Go - single parallel pass (up to 74x faster) |
| Circular dependencies | yes | yes |
| Unused files | yes | yes |
| Unused dependencies | yes | yes |
| Graph visualization (webapp / SVG / PNG) | yes | no |
| Unused exports / missing deps / boundaries | no | yes |
Where rev-dep is stronger​
- One config for the whole suite, adding unused exports, missing dependencies, module boundaries, restricted imports, and import conventions.
- Speed and CI-ready exit codes.
Where skott may still fit​
skott's interactive web app and static graph images are a real strength. rev-dep answers graph questions as text via the exploratory toolkit but renders nothing visual. Keep skott if the explorer is part of your workflow.
Which should you choose?​
- Want an interactive graph explorer? skott.
- Want the same checks plus exports, missing deps, and architecture rules enforced fast in CI? rev-dep.
Migrating​
See Migrating from skott.