@zuplo/editor@1.0.35074213265
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found library entrypoints without lifecycle scripts and resolved the flagged code to editor integrations, bundled UI components, and editor worker behavior. The network endpoints are Zuplo services, and no concrete malicious behavior was identified.
Decision evidence
public snapshot- package.json exposes library entrypoints; the inspected manifest defines no lifecycle scripts.
- The flagged configuration code detects editor integrations and creates editor deep links; the other flagged location styles Monaco cursors.
- The web bundle references editor and GraphiQL components, while its configured API, CDN, MCP proxy, and assistant endpoints are Zuplo services; assistant URL overrides are limited to localhost or agent-z worker hosts.
- The worker bundles contain editor error handling, CodeMirror cursor measurement, and TypeScript handling of Node built-in module names; the child_process match is part of that module list.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/client/static/js/main-qHfnnuKa.jsView on unpkg · L1572Source 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.35074213265.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35074213265 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.