1. Package B contains the faulty Dependency 1 1.0.0. 2. Package A contains the correct Dependency 1 1.0.1.
This is the best case scenario in this situation: Package A is not subject to the security problems of Dependency 1 1.0.0. Package B IS of course, but critical parts of your code are not exposed. If these were the only two packages involved, it would be simple. However the problem arrises from having LOTS of packages, and thus wanting to dedupe, which then leads to having to resolve these semver ranges, or being left with the unfortunate indeterministic behavior of sometimes these being distinct installations and sometimes not.
Thus, to achieve the desired result above AND ensure packages are only installed once on disk, you want to dedupe at the FILESYSTEM level. This is how ied behaves (and I encourage everyone to take a look at its implementation, it is very well done). Essentially, every package is installed and contains symlinks to their dependencies, that way it only takes up space on the hard disk once. However, thanks to node's treat-symlinks-as-real-filepaths option, as far as node is concerned these are distinct installations (as if you had done no deduping at all). Now you have the result from above AND the minimum space on disk.
> Package A contains the correct Dependency 1 1.0.1.
What happened to "Package A was written when Dependency 1 was at version 1.0.0."?
If someone in the pinned-version universe was able to update package A to include 1.0.1, the equivalent coder in the semver universe should have updated package A to require "<2 >=1.0.1". Semver dependencies should never lag in necessary updates vs. pinned dependencies in a fair comparison, because they can set an exact minimum.
It all depends on what sense you provide to the terms: "minor version" and how you expect your software to be built.