@zuplo/editor@1.0.38362879877
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the reviewed flagged locations resolve to editor metadata, styling, and compiler/editor code. The scanner’s invisible-character and execution-related matches did not establish an attack.
Decision evidence
public snapshot- package.json exports library and app modules; the inspected manifest has no lifecycle scripts.
- The flagged chunk location lists Cursor and WebStorm editor-opening protocols and detects `.cursor` and `.idea` files as editor metadata.
- The flagged API bundle location styles editor cursor classes; it does not configure an AI agent.
- The server chunk proxies a test request and returns a local gateway error when that request fails.
- The frontend bundles reference editor assets; the TypeScript worker includes a list of Node module names as compiler data.
- The CodeMirror bundle uses a zero-width space in browser layout handling, consistent with editor behavior.
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.38362879877.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38362879877 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.