@zuplo/editor@1.0.38766076269
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no lifecycle hooks, and the inspected runtime behavior is consistent with a local development editor. The scanner's flagged locations do not establish a concrete attack.
Decision evidence
public snapshot- The manifest exports local editor modules, packages the dist directory, and has no lifecycle script entries.
- The editor route uses a saved editor choice and returns a URL for opening a project file; it does not write agent configuration.
- The flagged .cursor references are editor detection metadata and Monaco cursor styling.
- The large bundles include the editor application and browser workers; the TypeScript worker contains a list of Node built-in module names.
- The inspected source does not establish credential collection, unconsented configuration changes, or malicious code execution.
- Scanner labels identify structural and Unicode concerns, but inspected source locations show editor behavior and worker content rather than an attack chain.
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.38766076269.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38766076269 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.