Display internal libraries/packages as service dependencies

[Machul84126]

Use Case

In our architecture, many of our services rely on shared internal libraries and packages (e.g., for common coding utilities, health-checking, etc.). Currently, it is difficult to track which services depend on which specific internal libraries within EventCatalog.

A concrete example: when we need to release an update or a security patch for an internal library, a developer needs to quickly identify all the services that use it so they can be updated. We discussed using the existing badges feature for this (e.g., adding a badge for each library), but if a service uses 5 or more internal libraries, the badges section quickly becomes chaotic and visually overwhelming.

Proposed Solution

It would be incredibly helpful to have a dedicated way to display libraries as service dependencies for purely informational context.

Ideally, EventCatalog could support this by:

1. Allowing us to define "Libraries" (or "Packages") as first-class citizens, similar to how we define APIs or Entities.
2. Listing these libraries in the navigation bar for easy access.
3. Providing a dedicated page for each library where developers can read its README.
4. Displaying a clear dependency graph or list showing which services rely on a particular library, making cross-service updates much easier to manage.

Implementation Notes

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.
• If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.