Describe the bug
While digging through npm.devminer.xyz/registry I came across a package named --------------------------------------------------------------------------------------------------------------------------------whynunu. The package shows up in the search (see also npm), but clicking the link for the exact match leads to a 404.
npmjs.com can list the package indirectly but serves a 404 for it as well.
Considering that only legacy or 1337 packages will be affected by this disrepancy there may be nothing to do here, but I thought it would be worth to call out at least.
Additional context
No response
Logs
Describe the bug
While digging through npm.devminer.xyz/registry I came across a package named
--------------------------------------------------------------------------------------------------------------------------------whynunu. The package shows up in the search (see also npm), but clicking the link for the exact match leads to a 404.npmjs.com can list the package indirectly but serves a 404 for it as well.
Considering that only legacy or 1337 packages will be affected by this disrepancy there may be nothing to do here, but I thought it would be worth to call out at least.
Additional context
No response
Logs