@inchurch/matcha-components@22.38.7
[Link to the project](https://bitbucket.org/inradar/design-system/src/master/).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe broad storage deletion is limited to an explicit, confirmed page-builder action, so the source does not show an attack running automatically. The confirmation describes clearing the canvas, while the implementation clears all origin storage, creating a destructive-action risk that merits a warning.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes Clear canvas and accepts the confirmation.
Impact
This can delete unrelated application state stored under the same origin.
Mechanism
The handler clears the editor canvas, then calls localStorage.clear().
AI rationale
The broad storage deletion is limited to an explicit, confirmed page-builder action, so the source does not show an attack running automatically. The confirmation describes clearing the canvas, while the implementation clears all origin storage, creating a destructive-action risk that merits a warning.
Evidence
fesm2022/inchurch-matcha-components.mjs
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The page-builder handler asks for confirmation, clears the canvas, then calls localStorage.clear(), which removes all local storage for the origin.
- The command is presented in the toolbar as “Clear canvas.”
- When the editor initializes with empty content, it invokes only GrapesJS’s core canvas-clear command.
Evidence against
- The package is an Angular component library with no lifecycle scripts declared in its manifest.
- The storage-clearing handler requires a user action and confirmation; it does not run during initialization.
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.38.7.
See all versions of @inchurch/matcha-components for other recorded verdicts.
- Review the evidence and your use of @inchurch/matcha-components@22.38.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.