@zuplo/editor@1.0.36835462198
Local development editor for the Zuplo CLI
AI Security Review
scanned 16d ago · by lpm-firewall-aiSource inspection found no lifecycle hooks or confirmed malicious behavior. The scanner’s agent-related matches resolve to editor metadata and styling, and the inspected file and API operations align with the editor’s stated purpose.
Decision evidence
public snapshot- package.json describes a local development editor and defines module exports without lifecycle scripts.
- The server’s agent-related entries identify editor protocols and files such as .cursor and .idea; they do not configure agent settings.
- The .cursor match in the editor bundle is used for cursor display styling.
- The web client obtains an access token and attaches it as a bearer token to API requests.
- The client bundle loads editor modules, and the JSON and TypeScript worker bundles contain editor worker code.
- The server exposes a file-save route for the editor, and the server entrypoint creates the editor with project filesystem and watched-directory adapters.
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.36835462198.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.36835462198 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.