[BUG] _npmUser value via npm view command return value is inconsistent

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

If I run the npm view <packagename> --json command on random different packages I will sometimes get a different _npmUser JSON output.

Usually, its a single line like this:
"_npmUser": "seijdeleon <sdeleon@berkeley.edu>",

But sometimes it's nested JSON:

  },
  "_npmUser": {
    "name": "openwalletfoundation",
    "email": "npm@openwallet.foundation",
    "actor": {
      "name": "openwalletfoundation",
      "email": "npm@openwallet.foundation",
      "type": "user"
    }
  },

Expected Behavior

I expect to get the same JSON format from the npm view command, but it appears as though some users are being treated differently.

Steps To Reproduce

Let me give you a few examples:

npm view buildkite --json | jq -r '._npmUser'
acegik nttduong77@gmail.com

npm view @blueskyproject/finch --json | jq -r '._npmUser'
seijdeleon sdeleon@berkeley.edu

npm view @bifold/core --json | jq -r '._npmUser'

{
    "name": "openwalletfoundation",
    "email": "npm@openwallet.foundation",
    "actor": {
       "name": "openwalletfoundation",
       "email": "npm@openwallet.foundation",
       "type": "user"
     }
}

As you can see, sometimes the npmUser value is a nested JSON object, and sometimes it isn't. This nested behaviour is new, and I just started seeing it in the last week or two. I'm assuming it is an API configuration change, but it affects the NPM CLI so I'm reporting it as a bug here.
There doesn't seem to be any distinction between an org or scoped NPM account or a non-scoped account, so I honestly don't know what the distinction is between users that are nested and ones that aren't.

Environment

• npm: 24.3.0
• Node.js: 11.4.2
• OS Name: MacOS Sequoia
• System Model Name:
• npm config:

prefix = "/usr/local"
; "user" config from /Users/REDACTED/.npmrc

//registry.npmjs.org/:_authToken = (protected)
registry = "https://registry.npmjs.org/"

; node bin location = /usr/local/Cellar/node/24.3.0/bin/node
; node version = v24.3.0
; npm local prefix = /Users/REDACTED/projects/githax
; npm version = 11.4.2
; cwd = /Users/REDACTED/projects/githax
; HOME = /Users/REDACTED
; Run `npm config ls -l` to show all defaults

This same issue is happening on all versions of npm and node that I've tested.

Start by reproducing the reported commands, npm view <packagename> --json and the three package examples, then compare the _npmUser values returned. Trace the npm view output path and determine whether the differing registry responses can be normalized; done means the command returns a consistent JSON shape for both examples.