@zuplo/editor@1.0.40379000583
Local development editor for the Zuplo CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s inspected behavior matches a local development editor: it serves a client, watches project files, and performs request and schema operations when used. The scanner flags resolve to ordinary editor code, and I found no malicious behavior.
Decision evidence
public snapshot- The manifest describes a local development editor and exposes JavaScript entry points; its package configuration contains no lifecycle scripts.
- The exported server starts its listener only when its start method is called, using the configured host and port.
- The test proxy forwards a request to the URL supplied in the request body, consistent with a local development editor feature.
- The schema route fetches schema files from the Zuplo CDN.
- The flagged CodeMirror bundle uses a zero-width space in editor layout and input handling; the flagged TypeScript worker contains TypeScript language-service code.
- The package has filesystem access for editor preferences and watches the configured project directory, consistent with its stated purpose.
- The worker’s child_process match is part of a built-in list of Node module names, not evidence of spawning a process.
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-DvuJqgyC.jsView on unpkgPackage source references dynamic require/import behavior.
dist/client/static/js/main-DvuJqgyC.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.40379000583.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.40379000583 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.