@zuplo/editor@1.0.37079892575
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no lifecycle hooks, and the flagged agent-integration locations resolve to ordinary IDE and editor data. Inspected client bundle excerpts are consistent with editor modules and workers; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json defines module exports and no lifecycle scripts; it exposes editor modules rather than an install command.
- The flagged agent-configuration location in the server chunk contains IDE file-detection and URL-template data.
- The flagged editor-bundle location contains cursor styling data, not agent configuration or a network operation.
- The large client bundles load editor modules and worker code; inspected worker prefixes initialize error handling.
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.37079892575.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.37079892575 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.