expgov

Appearance

expgovGovern your SDK export surface

Classify exports with tiers, catch drift between refs, and ship safer semver — read-only by default, TypeScript config only.

Get started
SDK
Install
expgov
📋

Barrel inventory

Flat counts, namespaces, tier and category breakdown — working tree or any git ref.

🔀

Diff and validate

Compare export surfaces between tags or commits; enforce tier rules and tsconfig ↔ package.json parity.

📈

Trend and timeline

Export counts across release tags; git log of barrel edits with summary metrics and cache coverage.

🕸️

Export graph

Namespace-first view of re-export targets, subpaths, and module fan-in with analytics summary.

🛡️

Read-only by default

Governance commands never edit your barrel — only init writes expgov.config.ts.

📦

SDK-ready core

@expgov/core exposes the same engines as the CLI — embed governance in your own hosts.

Install ​

CLI (terminal):

bash
pnpm add -D @expgov/cli
# or: npm install -D @expgov/cli

SDK (programmatic APIs only — not needed for CLI or config):

bash
pnpm add -D @expgov/core
# or: npm install -D @expgov/core

The @expgov/cli devDependency includes @expgov/cli/core for optional defineConfig in expgov.config.ts. npm blocks unscoped expgov (too similar to expo) — see Install.

Quick start ​

bash
pnpm add -D @expgov/cli
expgov init
expgov validate
expgov inventory
expgov diff HEAD
expgov timeline @4w
expgov graph

Install as a devDependency — the CLI tarball includes @expgov/cli/core for optional config types. See Install.

Documentation ​

TopicWhat you will learn
WorkflowsCopy-paste recipes for SDK setup, release review, and CI
Governance modelRead-only defaults, tiers, and what validate enforces
InstallRequirements, init, local dev, cache
SDK@expgov/core — install and host contract
Configurationexpgov.config.ts, tiers, @sdkTier
CommandsPer-command reference
CLI flags--json, cache, list truncation
JSON outputMachine-readable envelope for CI

Design principles ​

Governance without surprises. expgov separates inventory from enforcement. Commands are read-only except init. Tier rules live in TypeScript config you review in PRs — not hidden heuristics. Inspired by focused CLI tools: a thin host, clear defaults, and stable --json for automation.