@zuplo/editor@1.0.35187283247
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest declares editor exports and no lifecycle hook, and the inspected source excerpts show editor setup and browser editor components. Scanner indicators alone do not establish malicious behavior; no concrete attack was identified in the reviewed source.
Decision evidence
public snapshot- package.json exports editor modules and declares no install lifecycle hook.
- The server source creates the editor app from supplied filesystem, preferences, asset, and change-notification adapters.
- The indicated chunk location lists editor protocol schemes and file-detection settings.
- The indicated editor bundle location styles primary and secondary cursor elements.
- The required client files contain editor dependency mappings, editor worker code, or browser editor code; no concrete attack behavior was identified in the inspected excerpts.
- Scanner labels for network, child-process, and Trojan Source indicators did not establish malicious behavior in the inspected source excerpts.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/client/static/js/main-BcNxyjY5.jsView on unpkg · L1572A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/client/static/js/main-BcNxyjY5.jsView on unpkgFindings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.35187283247.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35187283247 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.