@zuplo/editor@1.0.37937033349
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest describes an editor package without lifecycle scripts, and the flagged agent-related locations concern IDE integration metadata and editor cursor styling. Scanner signals and large bundled assets did not establish malicious behavior in the inspected source.
Decision evidence
public snapshot- package.json identifies this as a local editor package and exports editor modules; no lifecycle scripts appear in the inspected manifest.
- The chunk location describes IDE names, URL templates, and detection files; the other flagged editor location styles cursor colors.
- The client bundles reference editor assets, and the worker files contain editor worker code.
- Searches of the main client and TypeScript worker found no `eval(`, `child_process`, or `process.env` matches; the worker’s `eval` match is a TypeScript declaration.
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-CNvNd0cC.jsView on unpkgPackage source references dynamic require/import behavior.
dist/client/static/js/main-CNvNd0cC.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.37937033349.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.37937033349 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.