COMPONENTS
Sign in

1. Release decisions

The decision is a release gate covering more than the software licence itself: demo assets, trade marks, third-party services, data provenance, dependencies and safety checks. It is a conservative operational judgement meant to stop the release process, not a legal warranty.

CLEARED — 125
Keep the pinned source and the MIT notice, pin the final build’s dependency versions in a lockfile, and it can become a release candidate.
REVIEW — 36
Install and publish actions stay disabled until the extra notices, assets, brands, data, third-party services or dependencies have been checked.
HOLD — 5
Some assets have no confirmable basis in rights, so nothing is published until they are replaced or shown to comply and re-reviewed.

2. Pinned sources

No implicit latest, branch or tag — everything is pinned to the commits below. Where we reuse source code, the relevant copyright notice and licence text stay in what we ship, even after TOBIRA has changed the colours, copy, layout and motion.

  • Componentry — 0a08e2e9f510ffc932393f8ece35d280f6b568d6 — MIT
  • Magic UI — 8e5e9eb7c2a7e7ac1440f413b847d7ddb9c67e0a — MIT
  • Motion Primitives — 92586e62a951eb9b6bfd1cc7c8a4e6e2ab6ba17d — MIT

A blanket MIT notice on a source does not automatically license the differently-licensed dependencies or assets a component reaches for.

3. The five on hold

  • componentry:infinite-image-field — On hold until the demo assets are separated from the third-party service terms and replaced with TOBIRA-owned assets.
  • componentry:scroll-split-card — On hold until external images with no confirmable basis in rights are replaced.
  • componentry:signature — On hold until the font licence and upstream notice are supplied.
  • magicui:client-tweet-card — On hold until it complies with X’s display, API, brand and external-data terms, or is reimplemented independently on invented data.
  • magicui:tweet-card — As above.

The individual reasons and clearing conditions for the 36 REVIEW items are recorded in a machine-readable ledger.

4. Operating rules

  1. New sources are pinned to a 40-character commit SHA and a licence snapshot is stored.
  2. The research gallery lets you watch the behaviour, but install and publish are disabled for anything at REVIEW or HOLD.
  3. Demo images, video, fonts, brands, geographic data and post data are checked separately from the code licence. As a rule we replace them with TOBIRA-owned assets and invented data.
  4. Every dependency of the final implementation is pinned to an exact version and re-audited from the lockfile or SBOM.
  5. Third-party notices ship with the distribution, and the release gate runs before anything enters the public index.
A preview rendering, looking like TOBIRA, and being publishable commercially are three different things. The decision is made against the final combination of code, assets and dependencies.

5. Notices and machine-readable data

THIRD_PARTY_NOTICES.md carries the three MIT licence texts that come with the pinned snapshots.

component-compliance.js records the 166-item tally, the 41 exceptions, the conditions for clearing them and the pinned commits, in machine-readable form.

The pre-release check runs the following command inside the repository.

node scripts/check-component-release.mjs
node scripts/check-component-release.mjs --release source-id:component-slug

This page and the ledger are operational records. They are not legal advice, and not a warranty that every third-party right has been identified.