What is an abandoned dependency?

An abandoned dependency is a software package its maintainers no longer update, so newly found flaws in it may never be fixed.

Share

An abandoned dependency is a software package its maintainers no longer update, so newly found flaws in it may never be fixed.

Why it matters

AI coding agents choose and install packages for developers, often from what they remember from training data. That memory can be months old, so agents keep installing tools that were archived after they were trained, including ones with known, unfixed flaws.

Example

In early November 2026, Glow reported that coding agents were installing archived MCP reference servers, the plug-ins that connect agents to tools, which had more than 17 million npm downloads since being archived; one has a flaw its maintainers will not fix.

How to defend against it

  • Check that a package is maintained before installing it, especially when an agent suggested it.
  • Scan agent configuration files for archived or deprecated packages and replace them with the service owner's own version.
  • Treat packages an agent picks as third-party code that needs review.
  • Pin versions and watch for archive notices. See the AgentSec Brief checklist.

Slopsquatting, agent skills supply chain, MCP tool poisoning.

Sources

From AgentSec Brief, the daily brief on securing agentic AI. Subscribe free at https://www.agentsecbrief.com