Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm on node:20.11-alpine3.18 fails with "Someone might have tampered with these packages since they were published on the registry!" #2047

Closed
mitar opened this issue Mar 17, 2024 · 3 comments

Comments

@mitar
Copy link

mitar commented Mar 17, 2024

Environment

  • Node.js Version: 20.11
  • Image Tag: node:20.11-alpine3.18

Expected Behavior

npm correctly installs packages.

Current Behavior

Since few days ago, installing npm packages inside node:20.11-alpine3.18 image is failing with:

Someone might have tampered with these packages since they were published on the registry!

Possible Solution

It looks like npm should be upgraded to 10.5.0 or newer:

npm/cli#7279

@nschonni nschonni closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
@mitar
Copy link
Author

mitar commented Mar 18, 2024

Why was this closed? Why not update npm in the Docker image for everyone?

@SimenB
Copy link
Member

SimenB commented Mar 18, 2024

New **NPM** releases are not tracked. We simply use the NPM version bundled in the corresponding Node.js release.

@mitar
Copy link
Author

mitar commented Mar 18, 2024

Thanks. But this now means that everyone using this package has effectively broken npm and has to increase their CI running time by upgrading npm first (after figuring out that one has to upgrade npm and that it is not that somebody is tampering with packages). I think this warrants an exception to the rule cited above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants