Dependencies & Supply Chain
This one is short on purpose. Every package your AI tool adds brings code you never read, and code that package depends on in turn.
Why it matters
You ask for a feature and the tool runs an install. One line in your package file can mean hundreds of packages underneath it, written by people you have never heard of.
You trust all of them with your build, and often with your keys. Most days that is fine. The days it is not fine, you find out from the news, not from your own app.
What it looks like when it goes wrong
- A package you use publishes a new version with something nasty in it, and your next install picks it up.
- A package that nothing maintains any more has a known flaw and never gets a fix.
- A flaw is reported in something three levels down that you did not know you had.
- A package you did not need is still in your project because the AI tried it once.
This has happened at scale. In September 2025 a self-replicating worm known as Shai-Hulud compromised over 500 npm packages. CISA reported that it scanned the environment for sensitive credentials, targeted GitHub personal access tokens and API keys, and sent what it found to an endpoint the attacker controlled. CISA alert, widespread supply chain compromise impacting npm.
What a proper check involves
- List everything your project depends on, including the packages underneath your packages.
- Check that list against known flaws, and then ask which of them your code can actually reach. Most cannot be reached. A few can.
- Find packages nobody maintains, and packages you installed once and never used.
- Commit your lockfile and install from it, so a surprise new version cannot slip in on its own.
- Know where your keys live at build time, so a bad package has less to steal.
The Kit section that does this check
The Self-Audit Kit runs this check for you, one prompt at a time.
- Section 8, The code you did not write: your dependencies, and which of their flaws you can actually reach.