@dotenvx/dotenvx@2.32.2
a secure dotenv–from the creator of `dotenv`
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the reviewed credential flows are gated by user configuration and an Armor session. The flagged secret pattern is an example in CLI help, while the added 1Password custodian accesses configured dotenvx keys through the local 1Password CLI.
Decision evidence
public snapshot- The package manifest lists development and release scripts, with no install or lifecycle hook.
- The `run` action passes credentials prepared for the requested command to the proxy configuration.
- The proxy does nothing when no environment value matches a configured credential placeholder; when active, it requires an Armor login and uses the session's HTTPS hostname.
- The proxy sends a request envelope containing credential ciphertext and placeholders to the configured Armor host's `/api/proxy` endpoint.
- The 1Password custodian reads a configured dotenvx private-key reference through the local `op` CLI.
- The credential proxy handles credential-bearing requests, and the 1Password integration invokes an external CLI; both behaviors are tied to dotenvx credential-management features and explicit configuration.
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.32.2.
See all versions of @dotenvx/dotenvx for other recorded verdicts.
- Review the evidence and your use of @dotenvx/dotenvx@2.32.2 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.