Dependency hygiene

What it means

Dependency hygiene means knowing what the project imports and whether those packages are still appropriate. It includes vulnerable versions, abandoned libraries, unnecessary packages, and risky additions.

Why it matters for AI-written code

Coding agents often reach for libraries to move quickly. The same habit can add stale, vulnerable, or unnecessary dependencies that become part of the software supply chain.

Guard and Fleet context

Guard treats dependency hygiene as a recurring audit area. Fleet context matters because the same package risk can appear across many repositories at once.

How Enji Guard helps

Guard identifies dependency issues, explains the impact, and can prepare reviewable updates when the path is clear. Ambiguous package choices stay visible as issues instead of silent risk.