registry / @dotenvx/dotenvx / 2.25.0
@dotenvx/dotenvx@2.25.0
a secure dotenv–from the creator of `dotenv`
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe package has no install hook, and the flagged shell pipeline runs only through an explicit update command. Key uploads and login requests are directed to Dotenvx Armor as part of its documented managed-key feature; no unrelated collection or concealed behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Consumers use the library or explicitly run CLI commands such as update, login, or Armor operations.
Impact
No unsolicited collection or execution was identified. Explicit Armor use uploads the selected key material to the Armor service as part of that feature.
Mechanism
File and OS secret-store operations support local key management. Armor requests use the configured Armor service; the update command's shell pipeline is limited to an explicit command invocation.
AI rationale
The package has no install hook, and the flagged shell pipeline runs only through an explicit update command. Key uploads and login requests are directed to Dotenvx Armor as part of its documented managed-key feature; no unrelated collection or concealed behavior was found.
Evidence
.env.env.keys.git/hooks/pre-commit
Network endpoints4
dotenvx.shdotenvx.sh/VERSIONarmor.dotenvx.com/api/armor/uparmor.dotenvx.com/oauth/device/code
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package declares no install lifecycle hooks; its scripts are development and release tasks.
- The shell pipeline is part of the explicit update command and runs only in the packaged-binary case.
- Encryption selects native, file, or Armor storage; the Armor upload occurs only in the Armor branch.
- Armor uploads the private key with a bearer token to the configured Armor service.
- Login sends device and basic system information to the selected Armor service.
Evidence against
- The explicit update command runs a shell script downloaded from dotenvx.sh when used with a packaged binary.
- The help text contains a private-key-formatted example, which is presented as CLI usage documentation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystem
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedsrc/cli/help.jsView file
86patternName = private_key_openssh
severity = critical
line = 86
Critical
Critical Secret
Package contains a critical-looking secret pattern.
src/cli/help.jsView on unpkg · L8686patternName = private_key_openssh
severity = critical
line = 86
Critical
package.jsonView file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 2
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkgFindings
2 Critical1 High1 Medium8 Low
CriticalCritical Secretsrc/cli/help.js
CriticalSecret Patternsrc/cli/help.js
HighSemantic Analysis Limitedpackage.json
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencesrc/cli/actions/update.js
LowAi Review Evidencesrc/lib/transforms/encrypt.js
LowAi Review Evidencesrc/lib/api/postArmorUp.js
Affected versions and remediation
This report applies to @dotenvx/dotenvx@2.25.0.
See all versions of @dotenvx/dotenvx for other recorded verdicts.
- Review the evidence and your use of @dotenvx/dotenvx@2.25.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.