@inchurch/matcha-components@22.37.0
[Link to the project](https://bitbucket.org/inradar/design-system/src/master/).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install hooks, and the flagged Unicode controls appear in Arabic country labels. The page-builder does load remote scripts, but only when that UI component is rendered, and the referenced assets serve the editor functionality; no malicious behavior was identified.
Decision evidence
public snapshot- The manifest exposes an Angular ESM entry point and declares only tslib as a dependency; it has no lifecycle scripts.
- The page-builder loads resources from ngAfterViewInit when its component is rendered, rather than during module import.
- The GrapesJS resources come from unpkg.com/matcha-components/assets/page-builder; the image-editor plugin references versioned Toast CDN assets.
- The bidi controls flagged by the scanner occur in Arabic country-name strings in the country list.
- The page-builder injects remote scripts into the document, so rendering that component causes browser requests to external hosts.
Source & flagged code
8 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.37.0.
See all versions of @inchurch/matcha-components for other recorded verdicts.
- Review the evidence and your use of @inchurch/matcha-components@22.37.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.