This is an exciting new feature! We're currently testing it out, but already have some early feedback.

When minimum package age is enabled, we'd like the latest dist-tag (or potentially all dist-tags) to be re-mapped to the latest package that meets the minimum package age rule.

For example, if I type npm install undici I currently get:

npm notice undici: 6 versions blocked by package-firewall due to security policies (version cooldown). Request an override: https://github.com/enterprises//security/bypass-requests/package-firewall/new?ecosystem=npm&package=undici
npm error code ETARGET
npm error notarget No matching version found for undici@8.12.3.
npm error notarget In most cases you or one of your dependencies are requesting a package version that doesn't exist.

The latest version of undici (8.12.3) was published today and I'm testing with a 7 day cooldown period. In this scenario, instead of having latest point to the blocked 8.12.3, it would be a better user experience to point to 8.11.2. Obviously this would be a non-trivial algorithm; it would need to be semver aware as many packages maintain multiple major versions in parallel.

Without the dynamic dist-tag rewriting, we'd expect a very large number of override requests as developers type npm install for frequently updated packages they're adding for the first time.

i will try it and thanks for it