@zuplo/editor@1.0.35137166429
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection supports a clean verdict: the manifest describes a local editor, and the flagged agent and execution indicators resolve to editor behavior and compiler metadata in the reviewed excerpts. The scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- The manifest describes a local development editor and exports its runtime from dist; it declares no lifecycle hook.
- The .cursor match is part of IDE detection data, and the server route accepts a known editor preference for opening files.
- The editor.api2 match is Monaco cursor styling for editor cursor classes, not agent configuration.
- The main bundle shows a dialog for choosing an editor and saving that preference.
- The reviewed large-bundle excerpts show browser editor and worker code; the child_process match is within a string listing Node built-in module names, with no execution shown.
- Scanner findings include network and child-process references, but the inspected excerpts do not establish an attack path.
- Searches of the flagged CodeMirror file found no common bidirectional control characters used in Trojan Source attacks.
Source & flagged code
5 flaggedSource contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/client/static/js/codemirror-6ITIKbGP.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.35137166429.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35137166429 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.