@zuplo/editor@1.0.36833296891
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the flagged editor configuration code only discovers a local editor and constructs a URL for an explicitly selected preference. The worker and bundle findings inspected are consistent with editor functionality and do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines module entrypoints and contains no lifecycle scripts.
- Editor configuration stores a validated editor preference; opening a file constructs a URL for that selected editor after normalizing the project-relative path.
- The frontend loads the editor list and saved preference from its local editor API.
- The flagged worker code uses fetch for editor schema loading and includes child_process among TypeScript language-service module names; no package process launch is shown.
- The flagged editor bundle excerpt contains cursor styling code.
Source & flagged code
5 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/client/static/js/main-D2zJSZub.jsView on unpkgPackage source references dynamic require/import behavior.
dist/client/static/js/main-D2zJSZub.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.36833296891.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.36833296891 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.