@eventcatalog/core@5.5.0
<div align="center">
AI Security Review
scanned 15d ago · by lpm-firewall-aiDirect inspection resolved the scanner’s credential and evaluation hints: license claims are reduced to status and expiry analytics, GitHub credentials go to GitHub, and the flagged UI code renders search results and examples. The package has no install hook, and the inspected telemetry is tied to CLI use with opt-out controls or explicit cloud analytics configuration.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and lists ordinary development and build scripts; it has no install lifecycle hook.
- The flagged runtime operations are CLI process handling and EventCatalog catalog setup.
- The flagged search and schema-viewer code handles UI components and displays examples; the inspected excerpts show no code evaluation.
- The inspected dependency snapshots expose AI SDK hooks and Astro markdown and MDX rendering behavior.
- CLI telemetry has explicit opt-out checks and sends EventCatalog event metadata to its analytics endpoint; cloud inventory reporting requires enabled analytics, a tracking ID, and a write key.
- The local license file is parsed for claims, while GitHub tokens are used in requests directed to GitHub; reported license analytics contain status and expiry fields.
Source & flagged code
6 flaggedPackage source references dynamic code evaluation.
eventcatalog/src/components/Search/SearchModal.tsxView on unpkg · L138Package source references dynamic require/import behavior.
dist/chunk-754U4T7K.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to @eventcatalog/core@5.5.0.
See all versions of @eventcatalog/core for other recorded verdicts.
- Review the evidence and your use of @eventcatalog/core@5.5.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.