Course contentsShow
← Data Science
Lesson 2054 of 2,14547. Reproducible ResearchFree lesson

Dependency Management Best Practices

Strategies for keeping dependencies minimal, updating safely, auditing for security vulnerabilities, and documenting choices.

Dependency Management Best Practices

You'll learn strategic principles for maintaining healthy, secure, and minimal dependency trees in your data science projects.

Core Principles

Think of dependencies like ingredients in a recipe—you want exactly what you need, nothing more, and you want to know those ingredients are safe and fresh.

Keep Dependencies Minimal

Every dependency you add is a potential maintenance burden and security risk. Evaluate whether you truly need a library or if standard library features suffice. Ask: "Does this 50-line utility justify adding an entire package?"

Update Safely and Deliberately

Don't blindly upgrade all packages at once. Use a staged approach:

  1. Read changelogs before updating
  2. Test updates in development first
  3. Pin critical production versions in requirements.txt or pyproject.toml
  4. Update dependencies regularly (not just when things break)

Audit for Security Vulnerabilities

Regularly scan your dependencies for known vulnerabilities:

  • Use tools like pip-audit or GitHub's Dependabot
  • Subscribe to security advisories for critical packages
  • Have a process for responding to vulnerability alerts

Document Your Choices

Your future self (and teammates) need context:

  • Comment why specific versions are pinned
  • Note any compatibility constraints
  • Document workarounds for dependency conflicts
  • Keep a changelog of major dependency updates

Example Documentation

# requirements.txt
numpy==1.24.3  # Pinned: newer versions break sklearn compatibility
pandas>=2.0.0  # Flexible: we use stable APIs only
requests==2.31.0  # Security: CVE fixed in this version

Key Takeaway: Treat dependencies as living parts of your project requiring active maintenance—keep them minimal, update thoughtfully, audit for security, and always document the "why" behind version choices.