Drop dependencies that nothing imports any more
Packages installed for something that no longer exists, removed with install size measured.
The ticket
Remove dependencies that nothing in the project imports.
Acceptance criteria
- Each removal is confirmed unimported, including dynamic and configuration usage
- The build and suite pass
- Install size and dependency count are recorded before and after
- Tooling-only dependencies are checked separately from runtime ones
What lands as proof
A clean install and green build after removal, plus the size difference.
Why teams defer it
- A package used only by a configuration file looks unused to most tools.
- Each unused dependency is a small install cost and a full security surface, which is an unbalanced trade nobody notices.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: remove dependencies that nothing in the project imports. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means install size before and after, build green, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.