@zuplo/editor@1.0.36192973685
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts and exports local editor APIs. The flagged locations support IDE navigation and editor rendering, while the scanner’s child-process match in the TypeScript worker is a module-name string; no malicious behavior was identified.
Decision evidence
public snapshot- package.json defines module exports for the editor app and server APIs, with no lifecycle scripts.
- The flagged server location defines IDE names, deep-link templates, and files used to detect installed editors.
- The flagged client location styles editor cursors; it does not configure or mutate agent settings.
- The large client files are bundled application and editor-worker code; the worker’s child-process text is part of a list of Node module names.
- No malicious behavior or confirmed attack surface was identified in the inspected source.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/client/static/js/main-BHMm2_7C.jsView on unpkg · L12Source 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.36192973685.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.36192973685 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.