@zuplo/editor@1.0.38536484871
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest declares no install hooks, and the inspected agent-configuration locations concern IDE detection and cursor styling. The bundled editor and language-tooling code, including scanner-flagged dynamic behavior, does not establish malicious package behavior.
Decision evidence
public snapshot- package.json defines editor entrypoints and has no lifecycle script.
- The flagged editor-configuration location lists IDE names, URL templates, and files used for detection.
- The server API is created from caller-provided filesystem, preferences, assets, and change interfaces.
- The second flagged location applies cursor theme colors in the editor.
- The GraphiQL bundle references editor and language-tooling chunks.
- The UI bundle references editor and GraphiQL chunks.
- The UI bundle references editor and GraphiQL chunks.
- The JSON worker is bundled client-side code; the TypeScript worker is also a client-side bundle.
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.38536484871.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38536484871 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.