log-llm-config@1.5.25
CLI helpers for logging hardware UUIDs and posting startup payloads to Optimus Security.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends identifying user and project metadata to its vendor endpoint during runtime collection. The source does not show the raw Codex token being sent or install-time exfiltration, so this is suspicious telemetry rather than malicious credential theft.
Decision evidence
public snapshot- The Codex collector reads identity claims from ~/.codex/auth.json and adds them to its collected record.
- The config runner collects Codex usage data and sends collected records to the configured endpoint.
- Startup metadata includes GitHub, organization, repository, branch, commit, and user profile details, and is posted to the endpoint.
- The default endpoint is https://app.optimuslabs.io/.
- The Codex collector extracts selected identity claims rather than forwarding the id_token itself.
- The prepare lifecycle script runs a build; no install-time data transmission is shown.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/log_config_files/collection/cowork_desktop_version_collector.jsView on unpkg · L1Package source references dynamic require/import behavior.
dist/tofu.jsView on unpkg · L19Findings
Affected versions and remediation
This report applies to log-llm-config@1.5.25.
See all versions of log-llm-config for other recorded verdicts.
- Review the evidence and your use of log-llm-config@1.5.25 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.