registry / @dotenvx/dotenvx / 2.31.0
@dotenvx/dotenvx@2.31.0
a secure dotenv–from the creator of `dotenv`
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has no install hook or import-time attack behavior in the reviewed entry points. Credential proxying is tied to user-configured Armor secrets and their declared destinations, while 1Password operations are explicit and use the local CLI.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Credential proxying requires a user-run dotenvx command with an Armor-configured env file; 1Password actions require explicit custody commands.
Impact
No unauthorized collection or unrelated account action was found. Runtime proxying handles only configured credentials and destination hosts.
Mechanism
Proxy requests containing configured placeholders are sent to the configured Armor host. The 1Password integration uses the local op CLI to store or retrieve keys.
AI rationale
The package has no install hook or import-time attack behavior in the reviewed entry points. Credential proxying is tied to user-configured Armor secrets and their declared destinations, while 1Password operations are explicit and use the local CLI.
Evidence
OS temporary directory: dxp-<random>/ca.pemOS temporary directory: proxy-preload.cjs
Network endpoints1
Configured HTTPS Armor hostname at /api/proxy
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has development and release scripts but no install lifecycle hook.
- The credential proxy requires Armor authentication and is activated only when a configured credential placeholder is present.
- Proxy credentials are forwarded only when a placeholder appears in an eligible request header for its declared host; redirects are rejected.
- The 1Password integration stores private keys in the user's 1Password account and is invoked through explicit custody commands.
- The critical-looking SSH key in help text is an incomplete usage example, not a usable credential.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedsrc/cli/help.jsView file
87patternName = private_key_openssh
severity = critical
line = 87
Critical
Critical Secret
Package contains a critical-looking secret pattern.
src/cli/help.jsView on unpkg · L8787patternName = private_key_openssh
severity = critical
line = 87
Critical
src/lib/helpers/ptyCommand.js#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
Findings
2 Critical2 High2 Medium6 Low
CriticalCritical Secretsrc/cli/help.js
CriticalSecret Patternsrc/cli/help.js
HighSemantic Analysis Limitedsrc/lib/helpers/ptyCommand.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltasrc/lib/custodians/local/onepassword.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencesrc/lib/services/validate.js
Affected versions and remediation
This report applies to @dotenvx/dotenvx@2.31.0.
See all versions of @dotenvx/dotenvx for other recorded verdicts.
- Review the evidence and your use of @dotenvx/dotenvx@2.31.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.