
Security News
arXiv Is Rate Limiting Authors Following a Flood of AI Slop Submissions
arXiv now limits authors to two submissions a month as AI slop overwhelms moderators, delays good papers, and sparks debate over applying the limit to everyone.
Environment variable management with Vercel-like developer experience.
npm install -g nvenv-cli
# or
bun add -g nvenv-cli
# or
pnpm add -g nvenv-cli
# Authenticate with your nv account
nv login
# List your workspaces
nv list
# Link to a workspace
nv link --workspace <workspace-id>
# Pull environment variables
nv pull --env production
# Pull to a custom file
nv pull --env development --output .env.local
nv loginAuthenticate with nv via browser. This will:
nv login
nv logoutLog out from your nv account and remove stored credentials.
nv logout
nv list (alias: ls)List all your workspaces.
nv list
# or
nv ls
nv linkLink the current directory to a workspace. Once linked, you can use nv pull without specifying the workspace ID.
# Link to a workspace
nv link --workspace <workspace-id>
# Show current linked workspace
nv link
Options:
-w, --workspace <id> - Workspace ID to linknv pullPull environment variables from a workspace and save them to a local file.
# Pull development variables (default)
nv pull
# Pull production variables
nv pull --env production
# Pull from a specific workspace
nv pull --workspace <workspace-id> --env production
# Save to a custom file
nv pull --env production --output .env.production.local
Options:
-e, --env <env> - Environment (production, preview, development). Default: development-w, --workspace <id> - Workspace ID (optional if linked)-o, --output <file> - Output file path. Default: .env.<env>.localThe CLI stores configuration in your system's config directory:
~/Library/Preferences/nv-cli-nodejs~/.config/nv-cli%APPDATA%\nv-cli\ConfigConfiguration includes:
apiUrl - API endpoint (default: https://nvenv.dev)accessToken - Authentication tokencurrentWorkspace - Linked workspace IDYou can customize the API URL using an environment variable:
export NV_API_URL=https://your-nv-instance.com
nv login
# 1. Login
nv login
# 2. List workspaces to find the one you need
nv list
# 3. Link to your project workspace
nv link --workspace abc123
# 4. Pull production variables
nv pull --env production
# 5. Pull development variables for local development
nv pull --env development --output .env.local
For CI/CD environments, you can skip the link step by always specifying the workspace:
nv pull --workspace $WORKSPACE_ID --env production --output .env.production
MIT
FAQs
nv CLI - Environment variable management with Vercel-like DX
We found that nvenv-cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Security News
arXiv now limits authors to two submissions a month as AI slop overwhelms moderators, delays good papers, and sparks debate over applying the limit to everyone.

Research
/Security News
A new GhostAction wave hits hundreds of GitHub repos, expanding CI/CD secret theft to cloud and AI credentials in source code and git history.

Research
/Security News
Tensorlake npm SDK version 0.5.144 was compromised in a ChainDrop / Shai-Hulud attack, delivering credential-stealing malware.