Yesterday I showed a repo's .npmrc beating my own user config. One line, ignore-scripts=false , in a folder I had just cloned, switched my protection off, and the install gave me no sign it had happened. The marker file was the only witness. That piece ended with a question I could not answer from memory, and it came from cryptostrapon in the comments: before you install, does npm config list show you the override, and does it say where it came from?
I had a guess. My guess was that it would show the final value and nothing else, a flat list with no blame attached. I ran it instead of arguing from memory, on my own machine, node v24.22.1 and npm 10.9.4, with the same test package and the same setup as yesterday: a user config saying ignore-scripts=true , a repo config saying false , and a hook that writes a marker file if it runs.
My claim, before the numbers: the four-second check that would have caught yesterday's override is not a nice habit for careful people.β¦