Connect npm to Quox
How do I connect npm?
Ask what npm needs, then store the token from your own terminal so it never goes near the chat.
What you get: the one field npm needs, where to put it, and a credential your agents can use without ever seeing the token.
Ask Quox
Section titled “Ask Quox”Ask in your own words:
How do I connect npm to Quox? What do I need to provide?
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 6ms
◐ DELEGATE │ delegate_to_agent agent_id=gitq ✔ DELEGATE │ delegate_to_agent agent_id=gitq │ 2 tools used, 2 tool outcomes · 29.2s
⛓ AEE │ envelope opened · ops.tool · delegate_to_agent ok
⛓ AEE │ envelope opened · stream_success
Connecting npm takes one thing: an npm access token. GITQ ran the connection guide for me. What to provide • An access token, either a granular token or an automation token. It's the only required field. • A label of your choice for the credential, for example npm-readonly . • Scopes: the guide doesn't list any. The integration reads package metadata, dist-tags and search results, and checks which account the token belongs to. Publishing uses OIDC trusted publishing, not this token. GITQ's recommendation, which is its own reading and not in the guide, is a read-only granular token. • Registry or org details: there is no field for a registry URL or an npm org. Nothing in the guide says private registries or org scopes are supported. npm's token docs are at https://docs.npmjs.com/about-access-tokens Where the token goes 1. Dashboard (recommended): open QuoxVault, then Credentials ( /vault/credentials ). You can also use Settings, then Integrations Vault. Click Add credential, choose npm as the type, add your label and paste the token. 2. CLI, in your own terminal: replace the <...> placeholders yourself. ───────────────────────────────────────────────────────────────────────────────────── printf '%s' '{"token":"<TOKEN>"}' | quox vault create --type npm --label "<LABEL>" --credentials-stdin ───────────────────────────────────────────────────────────────────────────────────── Or read it from a JSON file, which keeps the token out of your shell history. Delete the file once the credential is saved: ───────────────────────────────────────────────────────────────────────────────────── quox vault create --type npm --label "<LABEL>" --credentials-file <path-to-json-file> ───────────────────────────────────────────────────────────────────────────────────── Saving the credential runs a live connection test automatically. Please don't paste the token into chat. Once it's saved, tell me and I'll have GITQ test it as well. Until that test passes, npm isn't connected.
51.1s · 1 tool · 0 approvals
quox.✔ Machine verified against the CLI on 8 Nov 2026 · test report mw7x3p
Quox handed the question to its Git specialist, which read the vault’s connection guide for npm. It asked you for nothing secret, and told you to keep the token out of the chat.
Do it yourself
Section titled “Do it yourself”1. See what npm needs
Section titled “1. See what npm needs”quox vault typesID Name Descriptionnpm npm npm registry: package metadata, dist-tags, search, and to... Add --output json to see the full entry: one required field, token, which takes an npm granular or automation access token. The npm type has a live test, so Quox checks the token against npm itself.
2. Store the token
Section titled “2. Store the token”Put the field in a JSON file only you can read (0600), then:
quox vault create --type npm --label "npm read-only" --credentials-file npm-token.json--credentials-stdin reads the same JSON from standard input instead, so the token never touches disk. Creating a credential runs its connection test straight away; --no-test skips it.
3. Check it
Section titled “3. Check it”quox vault test <id> runs the connection test again at any time.
What just happened
Section titled “What just happened”Asking read the vault’s catalogue and connection guide, not your credentials, so nothing secret was read and no approval was needed. The token you store is encrypted on your own install. Agents borrow it for one tool call at a time and never see the value.
Check it yourself
Section titled “Check it yourself”quox vault list shows the new credential with its secret masked. quox vault activity shows who used it, and when.
quox vault delete <id> removes the credential. Revoke the token on npm too if you no longer need it.