@zuplo/editor@1.0.38742275715
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle script, and the required flagged locations resolve to editor detection, navigation, styling, and bundled editor support code. The inspected source did not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes editor library entrypoints and contains no lifecycle script; it describes a local development editor.
- The backend lists installed editor markers and constructs editor-opening URLs; the flagged `.cursor` entry is an editor detection marker.
- The editor UI reads editor choices from a same-origin API. The flagged `.cursor` styling in the editor bundle sets cursor colors.
- The other flagged bundles show editor asset loading, worker error handling, special-character detection, and TypeScript module names; no attack behavior was identified in these inspected excerpts.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/client/static/js/main-BUMZgWvV.jsView on unpkg · L9Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.38742275715.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.38742275715 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.