@eventcatalog/core@4.11.1
<div align="center">
AI Security Review
scanned 18d ago · by lpm-firewall-aiInspected source does not support the scanner’s malicious verdict: the flagged runtime locations implement search indexing, and the token-bearing request targets GitHub for repository content. The observed analytics paths are package-related, with cloud inventory reporting gated by explicit configuration.
Decision evidence
public snapshot- package.json exposes a CLI and ordinary development/build scripts; it declares no install lifecycle hook.
- The CLI entrypoint imports the package runtime. Reported account-action locations are search-index generation, Markdown file watching, and development/build commands; they do not perform authenticated account actions.
- The reported dynamic evaluation loads the Pagefind search module. ExamplesViewer renders code with a syntax highlighter.
- Analytics sends package and runtime metadata; cloud inventory reporting requires enabled analytics, a tracking ID, and a write key. GitHub tokens are sent to GitHub for requested repository content.
- The scanner’s credential-exfiltration and dangerous-source labels are not borne out by the inspected request paths: the GitHub token is used in authenticated GitHub content requests, and the cloud inventory request is explicitly gated by configuration.
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/copy-core.cjsView on unpkg · L36Findings
Affected versions and remediation
This report applies to @eventcatalog/core@4.11.1.
See all versions of @eventcatalog/core for other recorded verdicts.
- Review the evidence and your use of @eventcatalog/core@4.11.1 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.