Source snapshot bcc79fcc · Declared package version 2.0.5. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.
// Works in React Server Components — no 'use client' needed
import { renderIntegrationMarkdown } from '@lssm-tech/module.integration-hub/renderers';
export async function IntegrationCard({ id }: { id: string }) {
const integration = await fetchIntegration(id);
const markdown = renderIntegrationMarkdown({
id: integration.id,
name: integration.name,
description: integration.description,
category: integration.category,
status: integration.status,
connectionCount: integration.connections.length,
});
return <MarkdownRenderer content={markdown} />;
}
RSC directive boundaries
Hooks carry 'use client' — import them only in client components. Model types and the markdown renderer have no directive and are safe to import anywhere, including React Server Components. See AGENTS.md for the full boundary table and lint rules.
Deployment topology
validateIntegrationDeploymentTopology models service operator, runtime and data placement, credential custody, identity trust, API commercial mode, network policy, residency, and evidence placement as independent axes. It is a pure fail-closed validator: customer API keys cannot be assigned to an LSSM-only vault, and air-gapped profiles cannot depend on live central identity or remote managed data.
The model subpath re-exports the canonical provider-neutral topology contract from @lssm-tech/lib.contracts-integrations. The Hub accepts an optional
integration.topology-evidence read port for a secret-free, freshness-bounded provider receipt tied to an exact workspace or connection digest. Installing the port does not verify the provider by itself; only an adapter that has verified its native durable receipt may project this evidence.
What this package does NOT include
CompanyOS-specific chrome or view-models (those live in bundle.managed-companyos)
RedactedCredentialChip (stays in the bundle pending second consumer)
Any example fixtures or mock data (see examples/integration-hub)
Development
bash
bun test --cwd packages/platform/delivery/integration-hub
bun run --cwd packages/platform/delivery/integration-hub typecheck
Feature Hub profile
./hub exports IntegrationFeatureHub, defineIntegrationHub, and
installIntegrationHub. The profile uses the canonical platform.integrations
feature registry, mounts at /integrations, and depends only on the provider-neutral integration.catalog and integration.connection ports. Its route catalog covers detail, connections, syncs, configuration, credentials/secrets, health, audit, and installation; activation supports both managed credentials and BYOK secret references.
integration.topology-evidence is optional so existing installations remain compatible and missing proof remains explicit.
Declared capabilities.
Module Integration Hub
Scoped integration-hub module — 3 genuinely reusable primitives (useIntegrationData, useCredentialSetup, renderIntegrationMarkdown) promoted from examples/integration-hub. RSC-directive boundaries are explicit.
Use it to
Adopt scoped integration-hub module — 3 genuinely reusable primitives (useintegrationdata, usecredentialsetup, renderintegrationmarkdown) promoted from examples/integration-hub. rsc-directive boundaries are explicit
Requires
TypeScript
Choose another boundary when
The @lssm-tech/module.integration-hub package constraints do not match the target runtime or platform.
These are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.