@zuplo/editor@1.0.35077456762
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest has no install hook, and the cited flagged source locations show editor functionality rather than an attack. Static alerts alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json identifies a local development editor and exposes library entrypoints; it defines no install lifecycle hook.
- The flagged chunk lists editor protocols and project files for IDE detection, while the other flagged location renders cursor styles.
- The main bundle loads editor assets, and the TypeScript worker’s child_process match appears in a list of Node.js module names.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/client/static/js/main-DxYrJIuf.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-DxYrJIuf.jsView on unpkgFindings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.35077456762.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.35077456762 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.