@zuplo/editor@1.0.38643564145
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest presents a local editor package and defines no lifecycle hooks. The flagged source locations support ordinary editor behavior; scanner labels alone do not establish an attack.
Decision evidence
public snapshot- The manifest identifies a local development editor for the Zuplo CLI and exposes JavaScript entrypoints without lifecycle scripts.
- The flagged chunk describes ordinary editor-launch URL templates and IDE detection metadata.
- The flagged client bundle excerpt configures cursor styling; the other required bundle excerpts identify editor assets and worker modules.
- Scanner hints mention dynamic loading, network APIs, environment variables, large bundles, and unusual Unicode, but the inspected excerpts do not establish malicious behavior.
- The agent-integration locations correspond to IDE detection and cursor styling; no agent configuration mutation or credential transfer is established there.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/client/static/js/main-IITXJGuK.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.38643564145.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38643564145 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.