Dependency blindness
Reimplementing functionality that already exists in reachable code.
a.k.a. reinventiona.k.a. ecosystem-duplication
Description
The agent reimplements from scratch a function, class, or utility whose equivalent is already available in declared dependencies, the standard library, or reachable internal modules. Silent quality regression — the code may run correctly but increases surface area, duplicates effort, and drifts from ecosystem conventions. Distinct from Liu 2025's "Code Copycat" (intra-generation repetition): dependency_blindness is about cross-codebase reinvention.
Detection signals
- Emitted function signature matches an importable symbol in the project's declared dependencies.
- Emitted function body substantially overlaps (≥70% AST similarity) with a known stdlib symbol.
- Agent emits code despite a language-server suggestion to use an existing symbol.
- Emitted module reimplements a utility already present in the repository.
Prior work
- Mingwei Liu (2025) — The Code Copycat Conundrum: Repetition in LLM Code Generation
- Muhammad Usman (2017) — Taxonomies in Software Engineering: A Systematic Mapping Study and a Revised Taxonomy Development Method
Related failure modes
- Fabrication — Generating reference to non-existent APIs, packages, or symbols.
- Logic error — Correct API use, incorrect logic.
Mitigating tools
- pre-commit — Multi-language framework that runs configurable hooks before commits land — denies the commit on hook failure.
- Semgrep — Fast, rule-based static analysis with a pattern syntax that mirrors source code.
- sentrux — Real-time architectural sensor that scores codebase modularity, acyclicity, and redundancy as the agent writes.
- tree-sitter — Incremental parser toolkit that powers structural code analysis and symbol discovery.