One reporting standard. Every team, every report.

bino registry add resolves the dependency tree, verifies the digests, writes the files and records the dependency:

# follow the "latest" tag
bino registry add @acme/base-layout

# or pin an exact version
bino registry add @acme/quarterly-report@1.2.3

The result goes into bino.toml. An exact version stays where it is. A tag moves when you run bino registry update:

[dependencies]
"@acme/quarterly-report" = "1.2.3"
"@acme/base-layout"      = "latest"

You reference installed components by their scoped name and pass parameters, like any local document:

apiVersion: bino.bi/v1alpha1
kind: LayoutPage
metadata:
  name: commentary-page
spec:
  children:
    - kind: Text
      ref: "@acme/commentary"
      params:
        REGION: EU

A project can be published once it has a [package] table. include decides what ships:

[package]
name = "@acme/starter-kit"
description = "A reusable kit: an IBCS table, the style it wears and a logo asset."
tags = ["starter", "ibcs"]
category = "components"
visibility = "private"
compat-cli = ">=1.0.0"
include = ["components", "styles", "resources"]

# validate the package without creating a version
bino publish --dry-run

# publish a new, immutable version
bino publish --bump patch

Versions cannot be changed after publishing, so put --dry-run in front of every automated publish. --visibility public|private applies when the package is first created.

A pipeline installs the locked state and stops if anything differs:

export BINO_REGISTRY_TOKEN="bino_pat_..."

bino registry install
bino registry verify
bino build