GitHub and PyPI have introduced new time-based supply chain defences to limit the impact of malicious package releases.
GitHub’s Dependabot now applies a default three-day delay before updating dependencies. Meanwhile, PyPI will block new files from being added to releases older than 14 days.
Both measures aim to reduce the window for software supply chain attacks.
Dependabot adds a three-day cooldown
Dependabot is GitHub’s service for dependency updates. It reads project files and opens pull requests when newer package versions become available.
The service will now delay updates by 72 hours by default. This gives security tools and package maintainers more time to detect harmful releases.
Recent attacks have shown how quickly malicious packages can spread. Security researchers may flag a package within minutes. However, developers still need time to remove it.
GitHub said the three-day period balances security with the need for timely updates. Users can choose a shorter or longer delay through Dependabot’s cooldown settings.
Cooldown does not stop every package attack
The delay can help reduce exposure to newly published malicious packages. It is less effective against threats that remain undetected for longer periods.
GitHub recommends additional safeguards for stronger protection. These include lockfiles, restricted-scope tokens and fewer installation scripts in CI environments.
Lockfiles can pin projects to known package versions. Restricted tokens can also limit the damage from a compromised development workflow.
PyPI blocks changes to older releases
PyPI has introduced a separate time-based defence for Python packages.
Maintainers can no longer add new files to a release after 14 days. The change is designed to stop attackers from modifying old and trusted releases.
An attacker could otherwise compromise a publishing token or workflow. They could then add a malicious file to an existing package version.
PyPI said only a small number of projects upload files more than two weeks after a release. The platform therefore expects limited disruption for legitimate maintainers.
New rules follow major supply chain attacks
The changes follow several high-profile attacks across developer ecosystems.
Recent incidents include the chalk and debug attacks, the s1ngularity operation, the Shai-Hulud campaign and GhostAction.
PyPI said no confirmed past attack used the old-release poisoning method. However, the platform introduced the 14-day cut-off as a preventive measure.
Together, the new controls show a growing focus on time as a supply chain security layer.
0 responses to “GitHub and PyPI Add Time-Based Supply Chain Defences”