@zuplo/editor@1.0.38755103135
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource review supports a clean verdict: the manifest has no lifecycle scripts, the listener starts through an exported method, and the flagged source matches resolve to editor features or bundled tooling. Assistant requests are tied to user messages and use the package-aligned Zuplo worker.
Decision evidence
public snapshot- The manifest exposes local editor modules and has no lifecycle scripts; the server listener starts through an exported method.
- The flagged agent-related matches are editor features: one detects Cursor and saves editor preferences, while the other styles Monaco cursors. The open route uses a saved editor choice.
- The bundled assistant sends a request with user text and a bearer token after a non-empty message; its default Zuplo worker destination and permitted override hosts are package-aligned.
- The GraphQL console uses a HEAD request to check a URL's content type.
- The Unicode match is a zero-width character used by CodeMirror's layout probe; the JSON and TypeScript workers contain editor tooling.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/client/static/js/main-BUMZgWvV.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.38755103135.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38755103135 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.