registry / @zuplo/editor / 1.0.41117904454
@zuplo/editor@1.0.41117904454
Local development editor for the Zuplo CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package manifest has no lifecycle scripts, and the flagged worker match is a bundled TypeScript module-name catalog rather than process execution. The Unicode controls occur in CodeMirror’s special-character handling, while the server starts only through an explicit function call.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
No malicious automatic trigger was found. Server startup is exposed through an explicit serve function.
Impact
No malicious impact identified.
Mechanism
The worker contains a Node module-name catalog, and CodeMirror uses a Unicode-control pattern to identify special characters in edited content.
AI rationale
The package manifest has no lifecycle scripts, and the flagged worker match is a bundled TypeScript module-name catalog rather than process execution. The Unicode controls occur in CodeMirror’s special-character handling, while the server starts only through an explicit function call.
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a local development editor and defines module exports without lifecycle scripts.
- The TypeScript worker’s `child_process` match is part of a bundled Node module-name catalog; searches found no `spawn(` or `execFile` calls there.
- The CodeMirror bundle matches Unicode controls to display special-character markers in edited text.
- The server’s `listen` call is inside an explicit `serve(options, ...)` function.
- The editor app is constructed from caller-supplied options when `createEditorApp` is called.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
5 flaggeddist/client/static/js/codemirror-B7LWgdRs.jsView file
7contains invisible/control Unicode U+200B (zero width space)
height: `+(r-t)+`px`))}function d(t,n,r){var a=R(i,t),o=a.text.length,d,f;function p(n,r){return jr(e,B(t,n),`div`,a,r)}function m(t,n,r){var i=Lr(e,a,null,t),o=n==`ltr`==(r==`after`)?`left`:`right`;return p(r==
Critical
Trojan Source Unicode
Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/client/static/js/codemirror-B7LWgdRs.jsView on unpkg · L7dist/client/static/ts.worker-DJNYEI7I.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @zuplo/editor@1.0.41113817414
matchedIdentity = npm:QHp1cGxvL2VkaXRvcg:1.0.41113817414
similarity = 0.667
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/client/static/ts.worker-DJNYEI7I.jsFindings
2 Critical3 High4 Medium3 Low
CriticalTrojan Source Unicodedist/client/static/js/codemirror-B7LWgdRs.js
CriticalPrevious Version Dangerous Deltadist/client/static/ts.worker-DJNYEI7I.js
HighChild Process
HighCross File Remote Execution Contextdist/client/static/ts.worker-DJNYEI7I.js
HighSemantic Analysis Limiteddist/client/static/js/GraphiQLConsole-BUJsHcdm.js
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filedist/client/static/js/main-B08jEUyF.js
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @zuplo/editor@1.0.41117904454.
See all versions of @zuplo/editor for other recorded verdicts.
- Review the evidence and your use of @zuplo/editor@1.0.41117904454 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.