Skip to content

Packages

Every package of the workspace, each after the packages it depends on.

  • footman: A task runner with typed commands, nested groups, and instant shell completion.
  • forge: One interface to GitHub, Gitea, and GitLab — the livery ecosystem's forge.
  • strongroom: Content-addressed storage: one address space, every tenant.
  • toolroom
    • tools: Typed surfaces for command-line tools, generated from the tools themselves.
    • store: The pinned tool store over strongroom: specs, a machine-wide home, verified installs.
    • bench: The bench where toolroom's typed tool handles are made and refreshed.
  • git: Git access for the livery ecosystem: every call a function of the repository's root, through the tool store's pinned git.
  • workshop: The livery workshop, a footman plugin serving the whole dev loop.
    • extensions
      • cpp: C and C++ as languages, as an extension of the livery workshop: which of a package's files are sources, tests and test support, and the compilers the host must provide.
      • conan: A C or C++ package's conan recipe, as an extension of the livery workshop: its version stamped, its package built into the conan cache, and its release published to a conan remote, a folder or the forge's releases.
      • lfs: Git LFS for the livery workshop: the git-lfs tool locked, its hooks installed by every sync, and the LFS objects fetched by the rendered CI checkout.
      • mypy: mypy as a check of the livery workshop: the type checker, on every platform, configured by the root mypy.ini.
      • pyrefly: pyrefly as a check of the livery workshop: the type checker over every platform at once, configured by the root pyrefly.toml.
      • python: Python distributions, as an extension of the livery workshop: each package's version stamped, its wheel and sdist built, published and verified, its suite run against the installed wheel, and the layering rules over the python sources.
      • claude: Claude Code for the livery workshop: CLAUDE.md, the delivered guidance, .claude/ and the hook verbs the agent's tooling runs.
      • coverage: Each package's coverage floor in the livery workshop, judged on the union of what every CI leg measured, the record that carries it across runs, and the site's coverage pages.
      • nanobind: A python package whose extension module is C++, bound through nanobind, as an extension of the livery workshop: its platform wheels and sdist built for a release, on the runners the package names.
      • cmake: CMake as an extension of the livery workshop: a package's gate build, configured and compiled with Ninja, its tests run through ctest, and its native suites measured for coverage.
      • basedpyright: basedpyright as a check of the livery workshop: the type checker, and type completeness as its option.
      • changelog: Changelogs for the livery workshop: git-cliff writes each package's CHANGELOG.md entry as the release train releases it.
      • clang-format: clang-format as a check of the livery workshop: each native package's C and C++ sources, formatted by its own .clang-format.
      • clang-tidy: clang-tidy as a check of the livery workshop: each cpp package's sources, judged by its own .clang-tidy over its build's compilation database.
      • docs: The livery workshop's documentation site: its verbs build, serve and publish it from the workspace's docs/ and each package's docs/, and a lint step judges the links in the authored pages.
      • mkdocstrings: The python API reference on the livery workshop's docs site, a page per module, and the lint steps that judge the docstrings it publishes and the cross-references in them.
      • pytest: pytest as a check of the livery workshop: each python package's suite and documentation examples, configured by the root pytest.toml and .coveragerc.
      • ruff: Ruff as a check of the livery workshop: the formatter and the linter, configured by the root ruff.toml.
      • ty: ty as a check of the livery workshop: the type checker over every platform at once, configured by the root ty.toml.