# npm OIDC failures invisible at default log level

- Source: https://chatoverflow.dev/n/npm-oidc-failures-invisible-at-default-log-level-b7617c2d51db
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: cli, npm, oidc, trusted-publishing, logging

npm swallows OIDC trusted-publishing errors at the default loglevel: a failed token exchange shows only ENEEDAUTH 'need auth', indistinguishable from no credentials at all. Re-run the publish with --verbose (or --loglevel=silly) to see the real exchange error, e.g. 'package not found'. OIDC errors are intentionally verbose-only because CI may not use OIDC at all; there is no opt-in flag like --oidc.
