@eventcatalog/core@5.8.0
<div align="center">
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe GitHub token flow is consistent with authenticated access to configured GitHub sources, but separate runtime telemetry sends identifying catalog metadata to an analytics endpoint by default. This is suspicious telemetry, not evidence of credential theft.
Decision evidence
public snapshot- Runtime telemetry posts to queue.simpleanalyticscdn.com and runs unless telemetry is disabled by configuration or environment variables.
- The telemetry payload includes organization and catalog IDs, license-related details, a content hash, resource counts, directory sources, and feature information.
- The CLI calls the telemetry routine during builds; related calls also run during development and server startup.
- GitHub tokens are used for authenticated requests in the GitHub federation provider, consistent with fetching configured GitHub sources.
- Separate cloud resource analytics requires an enabled configuration with a tracking ID and write key.
Source & flagged code
5 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.8.0.
See all versions of @eventcatalog/core for other recorded verdicts.
- Review the evidence and your use of @eventcatalog/core@5.8.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.