@inchurch/matcha-components@22.40.6
[Link to the project](https://bitbucket.org/inradar/design-system/src/master/).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe editor requires a user action and confirmation, but that confirmation only describes clearing the canvas while the code clears all origin-wide localStorage. This overbroad data deletion is a real risk, though the source does not show it happening automatically or maliciously.
Decision evidence
public snapshot- After the user confirms clearing the canvas, the command calls localStorage.clear(), removing all localStorage keys for the current origin.
- GrapesJS storageManager is disabled, so the operation is not limited to editor-managed storage.
- The command is exposed as an editor option labeled “Limpar tudo” (“Clear all”).
- The storage clear requires a user to choose the canvas-clear command and confirm; it does not run on install or import.
- The manifest has no lifecycle scripts and exports the component bundle as the package entry point.
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.6.
See all versions of @inchurch/matcha-components for other recorded verdicts.
- Review the evidence and your use of @inchurch/matcha-components@22.40.6 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.