@zuplo/editor@1.0.36833894623
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected runtime behavior matches local editor integration. The scanner’s dynamic execution, network, and Unicode hints did not establish an attack in the cited source.
Decision evidence
public snapshot- package.json describes a local development editor and exposes library entrypoints; it declares no lifecycle script.
- The server’s editor configuration lists editor protocols and detection paths such as .cursor and .idea; the route saves a selected editor preference.
- The client editor UI loads and saves editor preferences through local API routes; the flagged editor.api2 match is cursor styling.
- The remaining cited files contain client bundle loading and editor worker code, including a TypeScript module-name list; no attack behavior was identified in the inspected excerpts.
Source & flagged code
5 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/client/static/js/main-D2zJSZub.jsView on unpkgPackage source references dynamic require/import behavior.
dist/client/static/js/main-D2zJSZub.jsView on unpkg · L12Findings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.36833894623.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.36833894623 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.