@lotics/cli@0.298.0
Lotics SDK and CLI for AI agents
AI Security Review
scanned 1mo ago · by lpm-firewall-aiDirect inspection resolves the scanner hints as ordinary authentication, opt-in diagnostics, documentation indexing, and user-invoked toolchain operations. No concrete malicious behavior or unresolved agent configuration capability was found.
Decision evidence
public snapshot- package.json has no registry install hooks or runtime self-dependency; prepublishOnly builds the release.
- The flagged agent integration location is an AGENTS.md documentation catalog entry, not an agent configuration write.
- Telemetry requires LOTICS_TELEMETRY=1 and posts diagnostic events to the active API's telemetry route.
- Saved credentials retain their profile's API destination; setup verifies a caller-supplied key against the selected instance.
- Child processes support app packaging and builds; dependency installation disables scripts, and upgrading requires the explicit upgrade command.
- The exported SDK receives its API credential and destination together from caller options.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L43784Findings
Affected versions and remediation
This report applies to @lotics/cli@0.298.0.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.298.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.