Intel / article

v0 now reads npm credentials from shared environment variables

Source: vercel.com
Author: Vishal Yathish
Date: Published Sep 18, 2026

Context

v0 can install a team's private software packages using access credentials stored in shared environment variables on Vercel. This lets generated applications use existing internal component libraries and design systems. The release note specifies NPM_ for the standard npm registry and NPM_RC for custom or multiple registries, with the variables scoped to Development or Preview.

Vercel says credentials can be marked sensitive and that v0 never exposes them to the model or writes them to the filesystem. The supported change is therefore both package access and a defined credential-handling path: teams can authorize dependency installation without putting the secret into their conversation with the model. The handling claim is Vercel's own statement, not an independent audit.

Key takeaways · AI-distilled

v0 supports two shared-environment-variable mechanisms for private packages: NPM_TOKEN for simple auth against registry.npmjs.org, and NPM_RC for configuring custom or multiple registries.
NPM_RC supports scoped registries (e.g. an @acme GitHub Packages scope) and can reference other environment variables, letting teams point v0 at a private registry like JFrog Artifactory without hardcoding secrets.
Credentials can be marked sensitive in Vercel and scoped to Development and/or Preview; v0 never exposes them to the model or writes them to the sandbox filesystem, and integration status is visible under Settings then Integrations.

Terms in this piece · Glossary

token — The chunk of text a model reads and writes in — roughly three-quarters of a word — and the unit AI usage is billed in.
sandbox — An isolated environment where AI-generated code or agent actions run without being able to touch anything real.

Read the source vercel.com