@zuplo/editor@1.0.38807503445
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and both flagged agent-integration locations resolve to normal editor behavior. The inspected source excerpts do not establish a concrete attack surface.
Decision evidence
public snapshot- package.json describes a local development editor, exports its modules, and defines no lifecycle hooks.
- The `.cursor` match is part of the supported editor list; its route reports supported editors and saves only a validated editor preference.
- The second flagged `.cursor` occurrence styles Monaco editor cursors.
- The inspected bundles include editor assets, a GraphiQL content-type check, and TypeScript and JSON workers; no attack behavior was identified in these excerpts.
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.38807503445.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38807503445 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.