@eventcatalog/core@4.7.12
<div align="center">
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe manifest has a CLI entrypoint but no install lifecycle hook. Reviewed runtime matches perform local search-index work or user-facing search, and build analytics is tied to a user-run build with resource reporting guarded by configuration; no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest exposes a CLI and contains no install lifecycle hook.
- The bundled search index code collects catalog records, writes Pagefind files, and removes the prior generated index.
- The indexed search build runs from the catalog build path; development rebuilds are tied to the local watcher and Markdown changes.
- The search component dynamically imports Pagefind and loads the search index for its interface.
- Build telemetry reports resource counts only when analytics is enabled and tracking credentials are configured; the build path also reports command usage.
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.7.12.
See all versions of @eventcatalog/core for other recorded verdicts.
- Review the evidence and your use of @eventcatalog/core@4.7.12 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.