@inchurch/matcha-components@22.40.2
[Link to the project](https://bitbucket.org/inradar/design-system/src/master/).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe page builder’s canvas-clear command clears all origin-scoped localStorage after a confirmation intended for clearing the canvas. Because this can remove unrelated application data, the package is suspicious rather than clean.
Decision evidence
public snapshot- The page builder’s confirmed canvas-clear command clears every key in the origin’s localStorage.
- The editor configuration disables GrapesJS storage management, so clearing all origin storage can affect unrelated application data.
- The storage clear requires the user to invoke the canvas-clear command and confirm it.
- The package manifest has no lifecycle scripts; its main export is an Angular component bundle.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
assets/page-builder/js/grapesjs-plugin-export.jsView on unpkg · L1Package source references a known benign dynamic code generation pattern.
assets/page-builder/js/grapesjs-plugin-export.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @inchurch/matcha-components@22.40.2.
See all versions of @inchurch/matcha-components for other recorded verdicts.
- Review the evidence and your use of @inchurch/matcha-components@22.40.2 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.