Released 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
A burst after one library's advisories that did not recur across four others.
Follow the connections
These are explicit references between records. The link itself does not establish support or intellectual influence.
Referenced by this record
- Public records show where a software update went, but not why, or whether anyone ran it finding
- Downloads show a new release taken up within two days, but not where it was installed or whether anyone ran it finding
- Published images show what software installed, and it was not always what its project had chosen 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 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
- When a widely used library releases, how much of the software built on it installs the new version because an installer resolved an open range, and how much waits for a maintainer to move a pin or lockfile? study
- Where does a software update go? investigation
Records that refer back here
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.