@zuplo/editor@1.0.35405313349
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or agent configuration behavior at the flagged locations. The editor detection entries and cursor styling are ordinary editor functions, and the package manifest exposes library entrypoints.
Decision evidence
public snapshot- package.json exports JavaScript entrypoints and defines no lifecycle scripts.
- The server chunk lists Cursor and other editors for detecting installed editors and opening files with their URL schemes.
- The flagged editor.api2 excerpt styles primary and secondary text cursors; it does not configure an agent.
- The large client bundles load editor components, while the workers provide browser-side editor services.
- The TypeScript worker imports a custom worker only when a worker path is configured.
Source & flagged code
4 flaggedSource 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.35405313349.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35405313349 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.