@zuplo/editor@1.0.34987767953
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no lifecycle hooks, and the inspected flagged matches serve editor and language tooling functions. The scanner’s child-process indicator is a Node module name in TypeScript worker parser data, not an execution call.
Decision evidence
public snapshot- package.json identifies this as a local development editor and exposes library entrypoints; it declares no lifecycle scripts.
- The server chunk lists Cursor as an editor option and uses its protocol to open files; the editor bundle’s `.cursor` matches are styling classes.
- The main client bundle requests the editor list and detection from a local service, consistent with editor preference behavior.
- The GraphiQL bundle performs a HEAD request for a displayed resource, and the JSON worker fetches schema text for language services.
- The CodeMirror file initializes the editor library; the TypeScript worker’s `child_process` match is within a list of Node module names for language parsing.
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.34987767953.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.34987767953 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.