@atlisp/mcp@1.9.3
⚠ Under reviewMCP Server for @lisp on CAD,support AutoCAD/GstarCAD/ZWCAD/BricsCAD or CAD platform compatible with AutoLISP
AI Security Review
scanned 23h ago · by lpm-firewall-aiThe source shows product-aligned health reporting and user-invoked autostart setup, with no confirmed attack behavior. The selected edge-js dependency source was unresolved, and it is used to load a native helper, so the package cannot be cleared from this inspection.
Decision evidence
public snapshot- The manifest declares edge-js, and the bundled runtime uses it to load the CAD helper DLL; the selected dependency source was unresolved in the supplied inspection record.
- The bundle sends hostname or configured client ID and CAD health metrics to its health-reporting endpoint when the server starts.
- The bundle exposes a native DLL helper whose behavior could not be established from the inspected JavaScript source.
- The only manifest lifecycle hook is prepublishOnly, which runs build scripts.
- Autostart persistence is activated by an explicit --install-autostart command.
- Health reporting sends operational status and CAD metrics to the package’s service endpoint.
Source & flagged code
9 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/atlisp-mcp.jsView on unpkgPackage source references child process execution.
dist/atlisp-mcp.jsView on unpkg · L1132Findings
Affected versions and remediation
This report applies to @atlisp/mcp@1.9.3.
See all versions of @atlisp/mcp for other recorded verdicts.
- Review the evidence and your use of @atlisp/mcp@1.9.3 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.