@zuplo/editor@1.0.35377476737
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install lifecycle behavior or concrete attack. The two flagged agent-related locations resolve to editor registry configuration and cursor styling; the other reviewed excerpts are consistent with the editor UI and its workers.
Decision evidence
public snapshot- package.json describes a local development editor and exposes local package entrypoints; it defines no lifecycle scripts.
- The flagged server chunk location maps supported editor IDs to editor URI schemes and project marker files; its routes list registered editors and validate saved preferences.
- The flagged API bundle location is cursor styling code, while the reviewed client and worker excerpts are consistent with editor rendering, metadata lookup, query refresh, error reporting, and compiler module-name data.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/client/static/js/main-CpUfvEzN.jsView on unpkg · L12Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/client/static/js/codemirror-6ITIKbGP.jsView on unpkg · L7Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.35377476737.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35377476737 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.