@lotics/cli@0.312.15
Lotics SDK and CLI for AI agents
AI Security Review
scanned 25d ago · by lpm-firewall-aiSource inspection found no malicious behavior. The manifest’s only lifecycle hook is prepublishOnly build, while the reported agent location is part of an embedded documentation index and telemetry is gated by an explicit environment opt-in.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and a library export; its only lifecycle hook is prepublishOnly, which runs the build.
- The reported agent configuration location is an embedded CLI documentation index entry, not a package-managed agent configuration write.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1; when enabled, it records invocation metadata and sends it to the CLI API endpoint.
- The CLI packages a project directory for its app toolchain when invoked, excluding node_modules, dist, TypeScript build info, and .git.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/src/cli.jsView on unpkg · L46813Findings
Affected versions and remediation
This report applies to @lotics/cli@0.312.15.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.15 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.