@eventcatalog/core@4.11.0
<div align="center">
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe scanner’s dynamic-evaluation and runtime-action matches resolve to loading the generated Pagefind module and local search-index operations. Build analytics reports package-aligned usage metadata, while Cloud inventory reporting has explicit configuration gates; the inspected source does not establish a concrete attack surface.
Decision evidence
public snapshot- package.json exposes a CLI and has no install lifecycle hook.
- The CLI builds a local Pagefind index from catalog records and writes it under the project output directory.
- Indexed search loads the generated local Pagefind module only when indexed search is active and the modal opens.
- The flagged example viewer renders supplied examples through ReactMarkdown and syntax highlighting.
- Build telemetry sends catalog metadata to an EventCatalog-branded analytics event; Cloud inventory reporting requires analytics.enabled, trackingId, and writeKey.
- The inspected runtime action matches are local search-index writes and rebuilds triggered by development or build activity.
- The reviewed credential-related code does not show catalog telemetry sending credentials; the reported hash is derived from catalog file paths and contents.
Source & flagged code
5 flaggedPackage source references dynamic code evaluation.
eventcatalog/src/components/Search/SearchModal.tsxView on unpkg · L137Package source references dynamic require/import behavior.
dist/migrations/message-channels-to-service-channels.cjsView on unpkg · L35Findings
Affected versions and remediation
This report applies to @eventcatalog/core@4.11.0.
See all versions of @eventcatalog/core for other recorded verdicts.
- Review the evidence and your use of @eventcatalog/core@4.11.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.