@inchurch/matcha-components@22.40.7
[Link to the project](https://bitbucket.org/inradar/design-system/src/master/).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe canvas-clear command calls global localStorage.clear() after a prompt that only describes clearing the canvas, so unrelated host-application data may be deleted. This is a destructive side effect in an otherwise ordinary UI component library, so I classify it as suspicious rather than malicious.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the page builder’s canvas-clear command and accepts its confirmation prompt.
Impact
Unrelated application state stored in localStorage may be lost.
Mechanism
The command clears the editor canvas, then calls localStorage.clear() without limiting deletion to editor-owned keys.
AI rationale
The canvas-clear command calls global localStorage.clear() after a prompt that only describes clearing the canvas, so unrelated host-application data may be deleted. This is a destructive side effect in an otherwise ordinary UI component library, so I classify it as suspicious rather than malicious.
Evidence
fesm2022/inchurch-matcha-components.mjs
Network endpoints2
unpkg.comviacep.com.br
Decision evidence
public snapshotAI called this Suspicious at 92.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The page builder’s confirmed “clean the canvas” action calls global localStorage.clear(), which can erase unrelated data saved by the host application on the same origin.
Evidence against
- The clear operation is behind an explicit confirmation prompt and is part of the page builder’s canvas-clear command.
- The manifest exports an Angular component bundle and declares only tslib as a dependency; the inspected HTTP lookups serve component features such as CEP address lookup.
Behavioral surface
DynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
NoLicense
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 Critical5 Medium5 Low
CriticalTrojan Source Unicodefesm2022/inchurch-matcha-components.mjs
CriticalTrigger Reachable Dangerous Capabilityfesm2022/inchurch-matcha-components.mjs
MediumDynamic Requireassets/page-builder/js/grapesjs-plugin-export.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumAi Review Evidencefesm2022/inchurch-matcha-components.mjs
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.40.7.
See all versions of @inchurch/matcha-components for other recorded verdicts.
- Review the evidence and your use of @inchurch/matcha-components@22.40.7 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.