@zuplo/editor@1.0.36861937463
⚠ Under reviewLocal development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe inspected manifest has no lifecycle hooks, and the flagged agent-configuration locations are IDE protocol metadata and editor styling. Large browser bundles were not fully resolved, so the source review does not support a confident clean or malicious verdict.
Decision evidence
public snapshot- package.json exposes editor APIs and declares no lifecycle scripts.
- The main entry imports the editor app and path-safety utilities.
- The flagged editor configuration bytes describe IDE protocols and cursor styling.
- The server proxies test requests and fetches schemas from Zuplo’s CDN.
- Large browser bundles remain only partially inspected, so their behavior is unresolved.
- The inspected manifest has no install-time hook; the cited runtime network calls serve test proxying and schema retrieval.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/client/static/js/main-DY4FmpMZ.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.36861937463.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.36861937463 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.