@zuplo/editor@1.0.38910504644
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 flagged locations are consistent with editor integration and bundled language tooling. Scanner hints alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json describes a local development editor and exports JavaScript entrypoints without lifecycle scripts.
- The server bundle detects Cursor’s .cursor directory and lists editor URL schemes, consistent with opening files in a local editor.
- The flagged editor bundle excerpt concerns Monaco cursor colors; the TypeScript worker excerpt lists Node built-in module names.
- The cited client bundles load editor, GraphiQL, CodeMirror, and JSON worker assets; no attack behavior was identified in the inspected excerpts.
- Static hints flag dynamic loading, network references, invisible Unicode, and analysis limits, but these hints do not establish harmful behavior in the inspected source.
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.38910504644.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38910504644 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.