Released finding
Pinned software moved to security fixes over weeks, a little faster after the release and again after the advisory, and neither drew most of the moves
A four-library reading of pin moves after security releases and advisories.
Follow the connections
These are explicit references between records. The link itself does not establish support or intellectual influence.
Referenced by this record
- Software built from open ranges took a new release within days; pinned software waited a month, and moved most often when a security advisory came finding
- When software built on a widely used library pins or locks it, what moves the pin: a new release, or a security advisory fixed by one? study
- Pinned software moved faster to security fixes that said so in their notes, mostly by people in the days after the release, but no larger share moved before the advisory finding
- Where does a software update go? investigation
Records that refer back here
- Where does a software update go? investigation
- Pinned software moved faster to security fixes that said so in their notes, mostly by people in the days after the release, but no larger share moved before the advisory finding
- When a Python project pins a library, the container recipe it keeps mostly installs what the pin names finding
- When a Python project pins a library, its test and build workflows almost always install what the pin names finding
- Does pinned software move sooner to a security fix that says so? Added up, it leans that way; library by library, we cannot tell finding
- Software built from open ranges took a new release within days; pinned software waited a month, and moved most often when a security advisory came finding
- Where does a software update go once it is released? finding
Reviews and checking history · 1
Navigation summary checked against the retained record. A record being written does not by itself mean that its study or investigation has ended.