@zuplo/editor@1.0.41113817414
Local development editor for the Zuplo CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the entry points expose editor functionality rather than starting an unrelated process. The flagged Unicode, worker, dynamic import, and network matches have identifiable editor or TypeScript purposes.
Decision evidence
public snapshot- The manifest describes a local development editor and exposes editor-related entry points; it contains no lifecycle scripts.
- The package README identifies it as part of the Zuplo CLI.
- The flagged zero-width character is used by CodeMirror in a text-layout probe.
- The worker’s `child_process` match is inside TypeScript’s built-in Node module-name list; no process-spawning call was found.
- The server fetches schemas from cdn.zuplo.com only for requests to its `/schemas/*` route.
- The UI dynamically loads Floating UI from cdn.jsdelivr.net as a fallback when CSS positioning features are unsupported.
- The package includes network access and dynamic import, but the inspected uses fit the editor’s schema-serving and UI behavior.
- Some bundled files are large, but the flagged worker behavior was identifiable as TypeScript tooling and no attack chain was found.
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.41113817414.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.41113817414 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.