@eventcatalog/core@5.7.5
<div align="center">
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package discloses default telemetry and provides opt-out controls, but the runtime event includes an organization name and catalog ID despite being described as anonymous. This is suspicious telemetry rather than credential exfiltration; the GitHub token warning does not show a token being sent through this reporting path.
Decision evidence
public snapshot- The package documents telemetry as anonymous, on by default, and opt-out.
- The runtime telemetry event includes the configured organization name and catalog ID.
- The event also includes license/trial data, catalog feature and resource metadata, and a catalog content hash.
- The telemetry code hashes catalog resource file paths and contents before reporting the hash.
- The CLI calls the telemetry reporter during a build.
- package.json declares no lifecycle scripts, so this telemetry is not sent during installation.
- The reported event fields do not include the GitHub token; the token is used in a separate GitHub source-provider function.
- Cloud resource analytics requires explicit cloud.analytics configuration with enabled, trackingId, and writeKey.
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.7.5.
See all versions of @eventcatalog/core for other recorded verdicts.
- Review the evidence and your use of @eventcatalog/core@5.7.5 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.