@dotenvx/dotenvx@2.13.0
a secure dotenv–from the creator of `dotenv`
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe suspicious primitives are reachable only through documented, user-invoked CLI commands and are package-aligned. There is no lifecycle hook, stealth execution path, or concrete malicious behavior in the inspected source.
Decision evidence
public snapshot- `src/cli/actions/update.js` shells `curl -sfS https://dotenvx.sh | sh`, but only under explicit `dotenvx update` and `process.pkg`.
- `src/lib/api/postArmorUp.js` sends a private key to the configured Armor service, but Armor commands explicitly request key management/upload.
- `package.json` has no preinstall, install, postinstall, or prepare lifecycle hook.
- `src/cli/dotenvx.js` wires update, Armor, extensions, and command execution to explicit CLI subcommands.
- `src/lib/helpers/executeDynamic.js` only launches a user-requested `dotenvx-<command>` executable from the project PATH.
- `src/lib/services/precommit.js` writes `.git/hooks/pre-commit` only when the user supplies `dotenvx precommit --install`.
- No source references to AI-agent configuration, broad persistence, credential harvesting, or hidden import-time execution were found.
Source & flagged code
5 flaggedPackage contains a critical-looking secret pattern.
src/cli/examples.jsView on unpkg · L86Package source references child process execution.
src/cli/actions/ext/scan.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @dotenvx/dotenvx@2.13.0.
See all versions of @dotenvx/dotenvx for other recorded verdicts.
- Review the evidence and your use of @dotenvx/dotenvx@2.13.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.