@dotenvx/dotenvx@2.30.0
a secure dotenv–from the creator of `dotenv`
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package is not malicious, but its CLI reports operation metadata—including local paths and key names—to the Armor service when a session is active. The opt-out does not establish that this runtime telemetry is disclosed, so this warrants a warning.
Decision evidence
public snapshot- CLI commands record operation names, outcomes, file paths, key names, and selected options as events.
- When Armor is enabled and a session token is available, the event backend sends those events to the session hostname.
- The package has an opt-out for this event backend through DOTENVX_NO_ARMOR or command options.
- The package entry point is src/lib/main.js; package metadata declares no install lifecycle scripts.
- Event metadata uses an allowlist and does not copy arbitrary command options or debug logs.
- The 1Password integration reads and stores keys through the user’s selected 1Password account; its set operation requires invoking the integration.
- Credential proxying requires configured placeholder credentials and an Armor token, and forwards requests to the configured credential host.
Source & flagged code
6 flaggedPackage contains a critical-looking secret pattern.
src/cli/help.jsView on unpkg · L87A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
Findings
Affected versions and remediation
This report applies to @dotenvx/dotenvx@2.30.0.
See all versions of @dotenvx/dotenvx for other recorded verdicts.
- Review the evidence and your use of @dotenvx/dotenvx@2.30.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.