@zuplo/editor@1.0.35253608947
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install lifecycle hooks and no concrete attack behavior. The flagged child-process and invisible-character matches resolve to editor-related source contexts.
Decision evidence
public snapshot- The manifest exports the editor runtime and contains no lifecycle script entry.
- The editor UI fetches local editor-list and saved-preference routes; the server returns stored editor preferences and validated editor details.
- The TypeScript worker includes `child_process` in a string of recognized Node built-in module names; the surrounding code checks imports.
- CodeMirror uses a zero-width space to measure browser rendering dimensions.
- Scanner flagged child-process use and invisible Unicode, but inspected source ties those matches to a worker module-name list and CodeMirror’s rendering measurement.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/client/static/js/main-BnegpwFb.jsView on unpkg · L1572A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/client/static/js/main-BnegpwFb.jsView on unpkgFindings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.35253608947.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35253608947 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.