Pip 26.1 Ships Dependency Cooldowns and Experimental Lockfile Support to Combat Supply Chain Attacks

2026-05-20 · Source: InfoQ · Field: Technology & Digital — Software Development & Engineering, Cybersecurity & Data Privacy · Depth: Intermediate, short

Summary

Pip 26.1, released last week, introduces dependency cooldowns and experimental "pylock.toml" lockfile support to enhance Python package supply chain security. Dependency cooldowns, enabled by "--uploaded-prior-to=P7D", prevent installation of packages published within a specified period, aiming to mitigate supply chain attacks by allowing time for detection. Analysis shows a 7-day cooldown would have prevented 80% of past attacks. However, this feature requires pairing with tools like Dependabot to avoid delaying critical security fixes. The release also adds experimental support for "pylock.toml" from PEP 751, allowing "pip install -r pylock.toml" to function, which is crucial for its widespread adoption given pip's default inclusion with Python. This lockfile support is experimental, with a "pip sync" command planned. Additionally, Pip 26.1 patched two CVEs (CVE-2026-3219 and CVE-2026-6357), updated vendored urllib3 to 2.6.3, and dropped support for Python 3.9.

Key takeaway

For DevOps Engineers managing Python dependencies in CI/CD pipelines, you should immediately consider implementing dependency cooldowns with Pip 26.1's "--uploaded-prior-to" flag. This significantly reduces your exposure to rapid supply chain attacks. While this may delay legitimate security fixes, you must integrate tools like Dependabot or pip-audit to monitor for critical patches. Additionally, begin experimenting with "pylock.toml" for more reproducible and secure builds, preparing for its eventual stable release and widespread adoption.

Key insights

Pip 26.1 enhances Python supply chain security through dependency cooldowns and experimental "pylock.toml" lockfile support.

Principles

• A waiting period for new package installations significantly reduces supply chain attack exposure.
• Standardized lockfiles are essential for reproducible and secure dependency management.
• Widespread tool adoption can accelerate new packaging specification integration.

Method

Implement dependency cooldowns using "pip install --uploaded-prior-to=P7D" to delay new package pulls. Install from lockfiles via "pip install -r pylock.toml".

In practice

• Configure a 7-day dependency cooldown to mitigate rapid supply chain compromises.
• Integrate Dependabot or pip-audit to monitor for critical security patches during cooldowns.
• Utilize "pylock.toml" for precise, reproducible dependency environments.

Topics

• Pip 26.1
• Dependency Cooldowns
• Supply Chain Security
• pylock.toml
• Python Packaging
• CVE Patches

Best for: CTO, VP of Engineering/Data, AI Architect, AI Security Engineer, Software Engineer, DevOps Engineer

Related on AIssential

• What's new in pip 26.1 - lockfiles and dependency cooldowns! — Pip 26.1 introduces lockfiles and dependency cooldowns, enhancing Python package management reliability.
• VS Code 1.123 Adds Two-Hour Extension Update Delay to Limit Supply Chain Attacks — Implementing update delays for software components can mitigate supply chain attack impact by providing a detection window.
• My AI Couldn’t See My Files — I Built a Zero-Dependency MCP Server — Building simple tools with standard libraries avoids unnecessary complexity and improves real-world reliability.
• datasette-export-database 0.3a2 — A dependency fix in datasette-export-database 0.3a2 significantly broadens its compatibility with Datasette versions.
• PyPI supply chain attack impacts data/ML pipelines (elementary-data) — A GitHub Actions flaw led to a PyPI supply chain attack using a ".pth" file for stealthy code execution.
• LiteLLM Supply Chain Attack: What Happened, Who’s Affected, and What You Should Do Right Now — A litellm supply chain attack compromised PyPI, exfiltrating credentials via malicious package versions.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.