@zuplo/editor@1.0.35395032411
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe source shows a concrete cross-origin exposure in the local editor API that can enable unauthorized project-file reads and writes. This warrants a warning as a vulnerability, but the inspected behavior does not establish package-driven malware or credential theft.
Decision evidence
public snapshot- The manifest describes a local development editor and exposes importable runtime entrypoints.
- The editor app reflects each request's Origin in CORS responses and permits cross-origin methods including GET and POST.
- The local server defaults to localhost on port 9100 and binds using its configured host and port.
- The API mounts project file routes backed by a filesystem rooted at the selected source directory; those routes read and write files by request path.
- The scanner's agent-related matches are editor-detection metadata and Monaco cursor styling, not agent configuration writes.
- The filesystem adapter rejects parent-directory segments when resolving project paths.
- The source supports a local editor API, but does not establish that the package automatically starts it or sends project files to a publisher-controlled endpoint.
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-BgPFNza7.jsView on unpkgPackage source references dynamic require/import behavior.
dist/client/static/js/main-BgPFNza7.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.35395032411.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35395032411 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.