@eventcatalog/core 3.39.2 → 3.39.4

package/dist/analytics/analytics.cjs

@@ -37,7 +37,7 @@ var import_axios = __toESM(require("axios"), 1);
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "3.39.2";
+var version = "3.39.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/analytics.js

@@ -1,7 +1,7 @@
 import {
   raiseEvent
-} from "../chunk-EC633RFS.js";
-import "../chunk-4NHSANWO.js";
+} from "../chunk-ONQOIF2X.js";
+import "../chunk-WLUQZCIH.js";
 export {
   raiseEvent
 };

package/dist/analytics/log-build.cjs

@@ -111,7 +111,7 @@ var import_axios = __toESM(require("axios"), 1);
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "3.39.2";
+var version = "3.39.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/log-build.js

@@ -1,9 +1,9 @@
 import {
   log_build_default
-} from "../chunk-2VUYMTYY.js";
-import "../chunk-EC633RFS.js";
+} from "../chunk-O2CZERUN.js";
+import "../chunk-ONQOIF2X.js";
 import "../chunk-4UVFXLPI.js";
-import "../chunk-4NHSANWO.js";
+import "../chunk-WLUQZCIH.js";
 import "../chunk-5T63CXKU.js";
 export {
   log_build_default as default

package/dist/{chunk-K2IR7X4Z.js → chunk-NSR4DZXS.js}

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-4NHSANWO.js";
+} from "./chunk-WLUQZCIH.js";
 
 // src/utils/cli-logger.ts
 import pc from "picocolors";

package/dist/{chunk-2VUYMTYY.js → chunk-O2CZERUN.js}

@@ -1,6 +1,6 @@
 import {
   raiseEvent
-} from "./chunk-EC633RFS.js";
+} from "./chunk-ONQOIF2X.js";
 import {
   countResources,
   serializeCounts

package/dist/{chunk-EC633RFS.js → chunk-ONQOIF2X.js}

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-4NHSANWO.js";
+} from "./chunk-WLUQZCIH.js";
 
 // src/analytics/analytics.js
 import axios from "axios";

package/dist/{chunk-Z3G6IPPF.js → chunk-PVOVC2UV.js}

@@ -1,6 +1,6 @@
 import {
   logger
-} from "./chunk-K2IR7X4Z.js";
+} from "./chunk-NSR4DZXS.js";
 import {
   cleanup,
   getEventCatalogConfigFile

package/dist/{chunk-4NHSANWO.js → chunk-WLUQZCIH.js}

@@ -1,5 +1,5 @@
 // package.json
-var version = "3.39.2";
+var version = "3.39.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/constants.cjs

@@ -25,7 +25,7 @@ __export(constants_exports, {
 module.exports = __toCommonJS(constants_exports);
 
 // package.json
-var version = "3.39.2";
+var version = "3.39.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/constants.js

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-4NHSANWO.js";
+} from "./chunk-WLUQZCIH.js";
 export {
   VERSION
 };

package/dist/docs/api/02-config.md

@@ -175,6 +175,30 @@ module.exports = {
 };
 ```
 
+### `security` {#security}
+
+<AddedIn version="3.39.2" />
+
+- Type: `Record<"checkOrigin", boolean> | undefined`
+- Default: `{checkOrigin: true}`
+
+Enables security measures for an EventCatalog website.
+
+These features only exist for pages rendered on demand (SSR) using server mode or pages that opt out of prerendering in static mode.
+
+By default, EventCatalog will automatically check that the “origin” header matches the URL sent by each request in on-demand rendered pages. You can disable this behavior by setting checkOrigin to false:
+
+You can read more on the Astro documentation [here](https://docs.astro.build/en/reference/configuration-reference/#security).
+
+```js title="eventcatalog.config.js"
+module.exports = {
+  output: "server",
+  security: {
+    checkOrigin: false
+  }
+};
+```
+
 ### `generators` {#generators}
 
 - Type: `Generator[]`
@@ -389,6 +413,7 @@ The `chat` property requires a Starter or Scale plan and `output: 'server'` to t
 
 ```js title="eventcatalog.config.js"
 module.exports = {
+  output: 'server',
   chat: {
     // Set to false to disable the AI chat feature entirely
     enabled: false,

package/dist/docs/api/03-domain-api.md

@@ -239,20 +239,50 @@ You can store these anywhere in your catalog, and your domain can just reference
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: My badge
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       # Or the name of the broker (e.g Kafka, EventBridge, etc)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 ### `specifications` {#specifications}
 
 <AddedIn version="2.6.0" />

package/dist/docs/api/04-service-api.md

@@ -220,19 +220,49 @@ An array of [flows](/docs/development/guides/flows/introduction) ids that are as
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: My badge
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 ### `specifications` {#specifications}
 
 <AddedIn version="2.39.1" />

package/dist/docs/api/05-command-api.md

@@ -142,20 +142,50 @@ An array of user ids that own the command.
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: My badge
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       # Or the name of the broker (e.g Kafka, EventBridge, etc)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 ### `schemaPath` {#schemaPath}
 
 Path to the schema of the message.

package/dist/docs/api/06-event-api.md

@@ -141,20 +141,50 @@ An array of user ids that own the event.
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: My badge
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       # Or the name of the broker (e.g Kafka, EventBridge, etc)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 ### `schemaPath` {#schemaPath}
 
 Path to the schema of the message.

package/dist/docs/api/06-query-api.md

@@ -139,20 +139,50 @@ An array of user ids that own the query.
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: My badge
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       # Or the name of the broker (e.g Kafka, EventBridge, etc)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 ### `schemaPath` {#schemaPath}
 
 Path to the schema of the message.

package/dist/docs/api/08-channel-api.md

@@ -207,20 +207,50 @@ An array of user ids that own the channel.
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: My badge
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       # Or the name of the broker (e.g Kafka, EventBridge, etc)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 ### `repository` {#repository}
 
 <AddedIn version="2.11.2" />

package/dist/docs/api/09-flow-api.md

@@ -316,20 +316,50 @@ Short summary of your flow, shown on flow summary pages.
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: My badge
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       # Or the name of the broker (e.g Kafka, EventBridge, etc)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 ### `editUrl` {#editUrl}
 
 <AddedIn version="2.49.4" />

package/dist/docs/api/10-entity-api.md

@@ -190,19 +190,49 @@ Each property can have the following fields:
 
 ### `badges` {#badges}
 
+<AddedIn version="3.39.4" />
+
 An array of badges that get rendered on the page.
 
 ```md title="Example"
 ---
   badges:
     - content: Core Entity
-      backgroundColor: blue
-      textColor: blue
+      backgroundColor: green
+      textColor: green
       # Optional icon to display (from https://heroicons.com/)
       icon: BoltIcon
 ---
 ```
 
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+```md title="Named color example"
+---
+  badges:
+    - content: Critical
+      backgroundColor: red
+      textColor: red
+---
+```
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
+
+```md title="CSS color example"
+---
+  badges:
+    - content: Custom
+      backgroundColor: "#6366f1"
+      textColor: "#ffffff"
+---
+```
+
 
 ### `editUrl` {#editUrl}
 

package/dist/docs/api/12-data-product-api.md

@@ -204,6 +204,8 @@ owners:
 
 ### `badges`
 
+<AddedIn version="3.39.4" />
+
 - Type: `array`
 
 Array of badges to display on the data product page.
@@ -225,8 +227,18 @@ Badge properties:
 | Property | Type | Required | Description |
 | -------- | ---- | -------- | ----------- |
 | `content` | `string` | Yes | Text content of the badge |
-| `backgroundColor` | `string` | Yes | Background color |
-| `textColor` | `string` | Yes | Text color |
+| `backgroundColor` | `string` | Yes | Background color (named token or CSS value) |
+| `textColor` | `string` | Yes | Text color (named token or CSS value) |
+
+#### Use named colors
+
+Set `backgroundColor` or `textColor` to a named palette token for automatic light/dark mode adaptation.
+
+Supported names: `slate`, `gray`, `zinc`, `neutral`, `stone`, `red`, `orange`, `amber`, `yellow`, `lime`, `green`, `emerald`, `teal`, `cyan`, `sky`, `blue`, `indigo`, `violet`, `purple`, `fuchsia`, `pink`, `rose`.
+
+#### Use any CSS color
+
+You can also pass any valid CSS color value directly: hex (`#ff0000`), `rgb()`, `hsl()`, `oklch()`, or a CSS variable (`var(--my-color)`).
 
 ### `repository`
 

package/dist/docs/development/guides/diagrams/05-comparing-diagrams.md

@@ -14,7 +14,7 @@ import AddedIn from '@site/src/components/MDX/AddedIn';
 <AddedIn version="3.3.0" />
 
 :::info EventCatalog Scale Feature
-Diagram comparison is available exclusively with the [EventCatalog Scale](/docs/development/deployment/licenses) license. This feature enables side-by-side visualization of different diagram versions.
+Diagram comparison is available exclusively with the [EventCatalog Scale](/docs/development/license-keys/plans) license. This feature enables side-by-side visualization of different diagram versions.
 :::
 
 The diagram comparison feature allows you to view two versions of a diagram side-by-side, making it easy to understand architectural changes and evolution over time.

package/dist/docs/development/license-keys/_category_.json

@@ -0,0 +1,12 @@
+{
+  "label": "License Keys",
+  "position": 11,
+  "collapsible": true,
+  "collapsed": true,
+  "link": {
+    "type": "generated-index",
+    "slug": "development/license-keys",
+    "title": "License Keys",
+    "description": "How to get and use license keys for EventCatalog plans (Starter, Scale) and integrations (OpenAPI, AsyncAPI, and more)."
+  }
+}

package/dist/docs/development/license-keys/integrations.md

@@ -0,0 +1,41 @@
+---
+sidebar_position: 3
+keywords:
+- licenses
+- integrations
+- plugins
+- openapi
+- asyncapi
+sidebar_label: Integrations
+title: Getting a license key for integrations
+description: How to activate EventCatalog integrations (OpenAPI, AsyncAPI, Backstage, and more) and get your license key.
+---
+
+EventCatalog integrations (sometimes called plugins) let you generate your catalog from sources you already have — OpenAPI specs, AsyncAPI documents, Backstage, federated catalogs, and more. You can see the full list on the [integrations page](/integrations).
+
+Each integration is licensed individually and comes with a **14 day free trial**. Activate one from your [integrations dashboard](https://eventcatalog.cloud/dashboard/integrations) — see the [Quick start in the overview](/docs/development/license-keys/overview#quick-start) for the full step-by-step.
+
+![Pick your integrations in EventCatalog Cloud](./images/pick-your-integraions.png)
+
+Once activated, your license key for the integration appears on your [API keys page](https://eventcatalog.cloud/dashboard/api-keys):
+
+![Your license keys in the EventCatalog Cloud API keys dashboard](./images/api-keys-dashboard.png)
+
+## Adding your license key to your catalog
+
+Copy the license key from your dashboard into your `.env` file. Each integration uses its own environment variable — the exact name is shown next to the key on your dashboard and in the integration's own documentation. For example:
+
+```bash title=".env"
+EVENTCATALOG_OPENAPI_LICENSE_KEY=your-license-key-here
+EVENTCATALOG_ASYNCAPI_LICENSE_KEY=your-license-key-here
+```
+
+Then configure the integration in your `eventcatalog.config.js` as described in the [integration's documentation](/integrations).
+
+## Trying multiple integrations
+
+You can activate as many integrations as you want from your [integrations dashboard](https://eventcatalog.cloud/dashboard/integrations). Each one has its own 14 day trial and its own license key.
+
+## Need more time?
+
+If 14 days isn't enough to evaluate an integration in your environment, email us at `hello@eventcatalog.dev` and we'll extend your trial.