@eventcatalog/core@5.6.0
<div align="center">
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found package-aligned analytics with opt-out controls and cloud inventory reporting gated by explicit configuration. The scanner’s credential and dynamic execution indicators did not establish an attack in the inspected code.
Decision evidence
public snapshot- package.json identifies the package and its EventCatalog repository; the CLI entry points to dist/eventcatalog.js.
- The CLI has no install lifecycle hook in its scripts, and runtime preparation handles the EventCatalog project directory.
- The flagged source files show UI, storage, and MCP imports; the resource counting chunk scans catalog content.
- The analytics code sends EventCatalog usage metadata and allows telemetry opt-out through configuration or environment variables.
- Cloud inventory reporting requires configured analytics to be enabled with a tracking ID and write key.
- The CLI sends usage and catalog inventory data to analytics endpoints during a command; the source provides opt-out controls and no inspected code sends credentials to those endpoints.
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/migrations/message-channels-to-service-channels.cjsView on unpkg · L35Findings
Affected versions and remediation
This report applies to @eventcatalog/core@5.6.0.
See all versions of @eventcatalog/core for other recorded verdicts.
- Review the evidence and your use of @eventcatalog/core@5.6.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.