log-llm-config
CLI helpers for logging hardware UUIDs and posting startup payloads to Optimus Security.
This report shows the evidence for log-llm-config@1.5.26. 0 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s network activity is tied to its documented Optimus inventory workflow and configured endpoint. The inspected credential-related collector extracts selected identity claims rather than transmitting the Codex bearer token.
Decision evidence
public snapshot- The only lifecycle hook is prepare, which runs the build.
- The README describes hardware UUID and startup-payload collection as the CLI’s purpose.
- The Codex collector extracts selected identity claims from auth.json; the inspected code does not send the bearer token.
- Collected config data is sent to the configured Optimus endpoint, with app.optimuslabs.io as the default host.
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.26.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of log-llm-config@1.5.26 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.