Security: Add cooldown period for uv to mitigate supply chain risks #3855
Unanswered
simbados
asked this question in
Core functionality
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe your core improvement
Currently in the dockerfile the dependecies are resolved with:
This introduces a large attack surface for supply chain attacks as the build will pull in the newest versions of all transitive dependencies (except the pinned versions in the constraint file). Pinning direct dependencies has only little effect as the bulk of dependencies are transitive.
Home assistant is already using uv, so it could introduce a cooldown period for dependencies (e.g. 1 day) which would look like this:
This could be combined with minimumReleaseAge from renovate, so direct dependencies are also only updated after a day.
Current limitations
Currently transitive dependencies are resolved at build time. Most transitive dependencies are referenced with >= which will pull in the latest version.
Technical benefits
Mitigation against most supply chain attacks
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions