@zuplo/editor@1.0.35637789723
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no install lifecycle hooks, and the flagged agent-related locations resolve to IDE protocol metadata and ordinary editor bundles. The scanner’s structural and bundle-size findings did not establish concrete malicious behavior.
Decision evidence
public snapshot- package.json exposes library entrypoints and has no lifecycle scripts.
- The flagged editor configuration entry describes IDE URL templates and project-file detection.
- The browser bundle presents API route types, while the GraphiQL bundle issues a content-type HEAD request for a supplied URL.
- The worker bundles handle editor messages; the large TypeScript worker includes standard editor language-service code.
- The inspected flagged code shows no concrete credential theft, persistence, destructive behavior, or unrelated agent configuration mutation.
- The package contains large bundled browser assets and bundled editor workers, which include dynamic and network-capable code in ordinary product contexts.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/client/static/js/main-C2cC5Aj-.jsView on unpkg · L12Source 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.35637789723.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35637789723 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.