Protocol

Audit the version before merging an AI-added dependency

A real dependency can still be a known vulnerable dependency.

About 1 min read

Before you use it

Use when
  • The package is legitimate, but the agent chose a version from stale training or an old example.

Keep this limit in mind

  • Vulnerability databases can lag or miss issues; high-risk components may need deeper supply-chain review.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Run the project's normal dependency and vulnerability checks on every new or changed dependency. Inspect the lockfile and release provenance, pin versions according to project policy, and separate 'latest' from 'approved.' Treat a clean scan as one signal, not a guarantee.

Steps

  1. Dependency audit run.
  2. Lockfile inspected.
  3. Version matches policy.
  4. Known vulnerability sources checked.
  5. License/provenance checks run if required.

An example

A valid library is rejected at the AI-suggested version because the project's scanner identifies a known vulnerability fixed in a later release.

Check your result

The dependency version is justified by current project security checks rather than model memory.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingAudit the version before merging an AI-added dependency

Evidence and sources
Supports

OWASP recommends auditing AI-suggested dependencies and versions against current vulnerability information rather than assuming a model knows recent CVEs or legitimate package names.

Dependency scanners also have coverage and freshness limits; manual package identity and provenance checks can still matter.

Secure Coding with AI Cheat Sheet · Hallucinated and Outdated Dependencies

Supports

NIST SSDF recommends integrating secure development practices into the software lifecycle rather than treating security as a separate late-stage review.

The framework is high-level and must be tailored to the organization's development model and risk.

Secure Software Development Framework (SSDF) Version 1.1 · SSDF overview

All sources (2)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details