@inchurch/matcha-components@22.36.0
[Link to the project](https://bitbucket.org/inradar/design-system/src/master/).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe clear-canvas command deletes all localStorage for the origin, a broader destructive effect than clearing the editor canvas implies. The action requires the user to invoke it and confirm, so this is suspicious rather than malicious.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the page builder’s canvas-clear command and confirms the prompt.
Impact
Other application data stored in localStorage for the same origin may be lost.
Mechanism
After clearing the editor canvas, the command calls localStorage.clear() without limiting deletion to editor-owned keys.
AI rationale
The clear-canvas command deletes all localStorage for the origin, a broader destructive effect than clearing the editor canvas implies. The action requires the user to invoke it and confirm, so this is suspicious rather than malicious.
Evidence
fesm2022/inchurch-matcha-components.mjs
Network endpoints2
unpkg.comuicdn.toast.com
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The page builder’s “canvas-clear” command asks for confirmation, clears the canvas, then calls localStorage.clear(), which removes all local storage for the site’s origin.
- The page builder loads its editor assets in ngAfterViewInit and uses an unversioned unpkg.com URL; this path is tied to using the editor component.
- The package manifest declares no lifecycle scripts.
Evidence against
- The storage-clearing code is attached to an explicit canvas-clear action and runs only after a confirmation prompt.
- The manifest exposes an Angular component bundle and declares only tslib as a dependency, consistent with a UI component library.
- Bidi controls flagged by the scanner occur in country-name strings containing Arabic text.
Behavioral surface
DynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscation
Source & flagged code
5 flaggedassets/page-builder/js/grapesjs-plugin-export.jsView file
1/*! grapesjs-plugin-export - 1.0.11 */
L2: !function(e,t){'object'==typeof exports&&'object'==typeof module?module.exports=t():'function'==typeof define&&define.amd?define([],t):'object'==typeof exports?exports["grapesjs-pl...
L3: //# sourceMappingURL=index.js.map
Medium
Dynamic Require
Package source references dynamic require/import behavior.
assets/page-builder/js/grapesjs-plugin-export.jsView on unpkg · L11/*! grapesjs-plugin-export - 1.0.11 */
L2: !function(e,t){'object'==typeof exports&&'object'==typeof module?module.exports=t():'function'==typeof define&&define.amd?define([],t):'object'==typeof exports?exports["grapesjs-pl...
L3: //# sourceMappingURL=index.js.map
Low
Eval
Package source references a known benign dynamic code generation pattern.
assets/page-builder/js/grapesjs-plugin-export.jsView on unpkg · L1fesm2022/inchurch-matcha-components.mjsView file
Findings
2 Critical1 High4 Medium5 Low
CriticalTrojan Source Unicodefesm2022/inchurch-matcha-components.mjs
CriticalTrigger Reachable Dangerous Capabilityfesm2022/inchurch-matcha-components.mjs
HighSemantic Analysis Limitedpackage.json
MediumDynamic Requireassets/page-builder/js/grapesjs-plugin-export.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowEvalassets/page-builder/js/grapesjs-plugin-export.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @inchurch/matcha-components@22.36.0.
See all versions of @inchurch/matcha-components for other recorded verdicts.
- Review the evidence and your use of @inchurch/matcha-components@22.36.0 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.