@decantr/registry

Support status: core-supported
Release channel: stable

Registry contracts, schemas, API client, ranking helpers, and content utilities for Decantr.

Install

npm install @decantr/registry

What It Exports

• strong types for patterns, themes, blueprints, archetypes, shells, and intelligence metadata
• ContentHealthReport types for registry content supply-chain health artifacts
• RegistryAPIClient for server-side and tool-side registry access
• @decantr/registry/client for web-safe API usage
• public schema exports for registry content, content health, and summary responses
• ranking and sorting helpers for public registry content
• blueprint portfolio metadata helpers for public All, Featured, Certified, and Labs registry cuts

Example

Node/runtime usage:

import { RegistryAPIClient } from '@decantr/registry';

const client = new RegistryAPIClient({ baseUrl: 'https://api.decantr.ai/v1' });
const results = await client.search({
  q: 'dashboard',
  type: 'blueprint',
  blueprintSet: 'featured',
});

Browser-safe usage:

import { createRegistryClient } from '@decantr/registry/client';

const client = createRegistryClient({ baseUrl: 'https://api.decantr.ai/v1' });
const summary = await client.getIntelligenceSummary();

Related Schemas

This package owns the canonical registry schemas published under @decantr/registry/schema/*, including content-health-report.v1.json for local content repository health reports emitted by decantr content-health.

Blueprint records can include blueprint_portfolio metadata. List/search summaries expose that metadata so clients can show public-facing blueprint sets without leaking internal maturity labels:

• all — supported public blueprints, excluding Labs and folded slugs by default
• featured — curated default discovery picks
• certified — blueprints with certified artifact metadata
• labs — opt-in experimental directions

Compatibility

@decantr/registry is part of the stable public Decantr package surface in the 2.x line.

• exported schema paths and documented client entrypoints are expected to remain stable across 1.x
• additive response fields may be introduced without breaking the stable contract
• breaking client, schema, or path changes require a major version

License

MIT