
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
A TypeScript utility package for managing environment variables with both programmatic API and CLI interface.
npm install -g update-env-utils
npm install update-env-utils
After global installation, you can use the update-env command:
update-env set API_KEY "your-api-key-here"
update-env set DATABASE_URL "postgresql://localhost:5432/mydb"
update-env get API_KEY
update-env list
update-env delete API_KEY
update-env set API_KEY "value" --file .env.production
update-env list --file .env.development
import EnvUpdater from 'update-env-utils';
const envUpdater = new EnvUpdater('.env');
// Set a variable
envUpdater.updateVar('API_KEY', 'your-api-key');
// Get a variable
const apiKey = envUpdater.getVar('API_KEY');
// List all variables
envUpdater.listVars();
// Delete a variable
envUpdater.deleteVar('API_KEY');
import EnvUpdater from 'update-env-utils';
const prodEnv = new EnvUpdater('.env.production');
prodEnv.updateVar('NODE_ENV', 'production');
const devEnv = new EnvUpdater('.env.development');
devEnv.updateVar('NODE_ENV', 'development');
new EnvUpdater(envFilePath?: string) - Creates a new instance with optional custom .env file path (defaults to '.env')readEnvFile(): Record<string, string> - Reads and parses the environment filewriteEnvFile(envVars: Record<string, string>): void - Writes environment variables to fileupdateVar(key: string, value: string): void - Updates or creates an environment variablegetVar(key: string): string | undefined - Gets the value of an environment variablelistVars(): void - Lists all environment variables to consoledeleteVar(key: string): void - Deletes an environment variable# Clone the repository
git clone <repository-url>
cd update-env
# Install dependencies
npm install
# Build the project
npm run build
# Watch for changes during development
npm run dev
npm run build - Compile TypeScript to JavaScriptnpm run dev - Watch mode for developmentnpm run clean - Remove dist directorynpm run start - Run the compiled main filenpm test - Run tests (placeholder)npm login
# Build the project
npm run build
# Publish (this will automatically run prepublishOnly script)
npm publish
# Or use the version bump scripts:
npm run publish:patch # 1.0.0 -> 1.0.1
npm run publish:minor # 1.0.0 -> 1.1.0
npm run publish:major # 1.0.0 -> 2.0.0
npm run build successfullydist/ directory contains compiled filesnpm pack and npm install -g ./update-env-utils-1.0.0.tgzupdate-env/
├── src/
│ └── main.ts # Main TypeScript source file
├── bin/
│ └── cli.js # CLI executable
├── dist/ # Compiled JavaScript (generated)
├── package.json # Package configuration
├── tsconfig.json # TypeScript configuration
└── README.md # This file
MIT
git checkout -b feature/amazing-feature)git commit -m 'Add some amazing feature')git push origin feature/amazing-feature)FAQs
A utility package for environment variable management
We found that update-env 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.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.