Vercel Sandbox adds managed credentials for private npm packages

Vercel Sandbox can now install a team’s private npm packages using credentials stored in team Shared Environment Variables. The update also supports custom registries including GitHub Packages and JFrog Artifactory.
- Vercel Sandbox now supports managed npm credentials.
- Credentials are stored in team Shared Environment Variables.
- GitHub Packages and JFrog Artifactory are supported.
- Tokens stay outside the sandbox during package installs.
- Users must update the Sandbox SDK or CLI to the latest version.
Private package installs from inside a sandbox
The update lets a sandbox use a team’s existing npm credentials when installing dependencies. Developers enable the capability by passing credentials: { npm: true } when creating a sandbox.
After the sandbox is created, project files can be cloned or copied into its working directory before running an install command such as pnpm install. This gives projects using private dependencies a supported way to install those packages within Vercel Sandbox.
Vercel says the feature works with custom registries as well as npm package sources. The announcement specifically names GitHub Packages and JFrog Artifactory as supported registries.
Tokens remain outside the sandbox
The credentials flow is designed to keep authentication tokens separate from the sandbox environment. According to Vercel, tokens stay outside the sandbox while the firewall adds authentication to install requests sent to the configured registries.
That means a coding agent can install dependencies without seeing the tokens themselves. The credentials are used for the package installation request, rather than being exposed inside the sandbox where the agent is operating.
This distinction matters for teams that need private packages in sandboxed development or agent workflows. They can provide access to their configured registries while keeping the underlying npm credentials outside the sandbox.
How to enable the feature
Vercel instructs users to update the Sandbox SDK or CLI to the latest version before using managed npm credentials. For the SDK, the announcement shows the command pnpm add @vercel/sandbox@latest.
The example uses the @vercel/sandbox package and creates a sandbox with npm credentials enabled. Users then run an install command after placing the project files in the sandbox’s working directory.
Vercel directs developers to its npm credentials documentation for setup instructions. For users working with private dependencies, the change adds a way to connect existing team credentials to sandbox installs without putting the tokens in the sandbox.
Vercel: Vercel Sandbox now supports managed npm credentials


