

An example: If Im ever going to sell my Nintendo Switch (1), I’m absolutely going to include the model number. The reason: It’s a launch day Switch. While this means that it is the oldest model and also the battery might have more wear than a newer model, it also suffers from an unpatchable hardware bug that allows you to hack the system (and run homebrew, pirated games, modded games,…).










If it’s a depdency nested deep in the dependency graph, that doesn’t necessarily mean I abandoned my project. I might be using this dependency of a dependency in my project and don’t notice anything, if there is a precompiled version for the (Python/Linux/…) distribution I’m running on my machine, so I might not notice that. It might even be, that I keep my dependencies up to date, but someone up the chain isn’t. And maybe there isn’t really a viable alternative to that one dependency that pulls that package in.