@zuplo/editor@1.0.38506973708
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found the flagged locations to be ordinary editor integration and styling code, and the manifest exposes library entrypoints without a lifecycle hook. The scanner hints did not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes the editor library and app entrypoints; no lifecycle hook is declared.
- The backend’s Cursor entry is an editor protocol template and project marker used by the editor preference and open-file routes.
- The other flagged location is Monaco cursor styling, not agent configuration.
- The large client bundles load editor, GraphiQL, CodeMirror, JSON worker, and TypeScript worker assets; no concrete attack behavior was identified in the inspected source.
Source & flagged code
4 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.38506973708.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38506973708 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.