Component licenses
TL;DR
- Every component declares a
license:incomponent.yml, as an SPDX expression. - Third-party code inside a component declares its own license under
vendored:. - A component with neither
license:nor aLICENSEfile is refused. - A public component whose license,
LICENSEfile, vendored tree or model file restricts commercial use is refused. - Pipelogic's own components use
LicenseRef-Pipelogic-Platform.
Declaring the license
Put license: at the top level of component.yml, beside name. The value is an SPDX license expression.
name: My Component
license: Apache-2.0
The component license covers the component's own code alone. A model or other file bound through a file slot carries its own license on that file.
Third-party code shipped inside the component declares its own license under vendored:. Each entry names the path, the upstream repository URL, the version and the SPDX license of that tree:
vendored:
- path: src/liveportrait
upstream: https://github.com/KwaiVGI/LivePortrait
version: 9b294b3d0536135442ea73cb01e6cb3ca7029dd3
license: MIT
What release checks do
A component with neither license: in component.yml nor a LICENSE file is refused:
component.yml: license missing; declare license or supply LICENSE
Rule build.license, "license declared":
The component declares the license its own code ships under, so whoever adds it to a backend knows what they may do with it. A model or other file bound through a file slot carries its own license on that file; the component license never covers or restates it.
Rule look.visibility, "public only under licenses that allow it":
A component visible to everyone ships only under licenses that allow any use: its license, its LICENSE file, the license of each tree component.yml declares under
vendored:, and the license of every file its team holds for one of its file slots (a file carrying the slot's tag). A license that restricts commercial use (CC-BY-NC, OpenRAIL, a custom LicenseRef) keeps the component private or workspace-only.
The fix the rule gives: set the component workspace-only, or license its code for any use, or replace the vendored tree or the slot's file with one whose license allows any use.
The Pipelogic Platform License
Pipelogic's own components declare license: LicenseRef-Pipelogic-Platform. The license allows use, including commercial use, on the Pipelogic platform and in deployments run through it.
It does not allow copying or redistributing the component outside the platform. Every other LicenseRef-* counts as restricting commercial use, so a public component cannot carry one.
The full text of the license:
Pipelogic Platform License 1.0
Copyright (c) 2026 Pipelogic
- Grant. Pipelogic grants any person or organization a non-exclusive, worldwide, royalty-free license to use this component, including for commercial purposes, on the Pipelogic platform and in deployments run through it, and to modify it for that use.
- Limits. The component may not be copied, redistributed, sublicensed or sold outside the Pipelogic platform, and may not be used to build a competing component registry.
- Third parties. Code and model files from third parties that ship with the component keep their own licenses, which the component names under
vendored:in its component.yml and on the files bound to its model slots. - No warranty. The component is provided "as is", without warranty of any kind. Pipelogic is not liable for any claim or damage arising from its use, except where the law does not allow this to be excluded.
Related
- Component contract — the
component.ymlfields. - File binding — the license of a file bound to a slot.
- Release semantics — publish and promote.