log-llm-config@1.5.18
CLI helpers for logging hardware UUIDs and posting startup payloads to Optimus Security.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI has a stated configuration and startup logging purpose, and the reviewed flow requires command invocation. However, it also reads Codex account identity and sends email and related identity fields with usage data without a disclosed opt-in or opt-out, which is suspicious identifying telemetry.
Decision evidence
public snapshot- The Codex collector reads identity claims including email and name from ~/.codex/auth.json.
- The collector adds identity fields, including email and account details, to the usage record.
- Running the config logging command collects local configuration and posts payloads to the configured endpoint.
- The package describes its purpose as posting startup payloads to Optimus Security.
- The network activity is part of the package's stated logging and startup reporting purpose.
- Collection and upload run when the CLI command is invoked; the reviewed entry point does not automatically run them on import.
- The collector decodes identity claims locally and does not include the Codex token itself in the record.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/log_config_files/collection/cowork_desktop_version_collector.jsView on unpkg · L1Package source references shell execution.
dist/log_config_files/runtime/trusted_restarts.jsView on unpkg · L84Findings
Affected versions and remediation
This report applies to log-llm-config@1.5.18.
See all versions of log-llm-config for other recorded verdicts.
- Review the evidence and your use of log-llm-config@1.5.18 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.