coherent.licensed
License management tooling for Coherent System and skeleton projects
Decision gist · record as of 2026-08-14
Yes, if you are building packages with coherent.build or skeleton and need automated license file injection. Install only as a build requirement in your build-system configuration, not as a runtime or development dependency. The low friction and active maintenance make it safe for this specific use case.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.9 or later.
- Intended for use during build only; not a runtime dependency.
- Low install friction with no runtime dependencies.
License · maintenance · safety
MIT (permissive) — MIT license permits commercial and private use with minimal restrictions. Suitable for projects with permissive licensing requirements.
last release 2025-06-02 (438 days) · last repo commit 2026-07-17
0 known vulnerabilities (OSV.dev, 2026-08-14) · 120,872 downloads/mo, #12,005 on PyPI
Alternatives
Verify before relying
# Install as build requirement in pyproject.toml
[build-system]
requires = ["setuptools", "coherent-licensed"]
# The plugin activates automatically during build
# License file is injected based on License Expression in metadata- How the plugin determines which license file format or location to use when injecting
- Whether the plugin works with all License Expression formats or has limitations
- Integration compatibility with build backends other than Setuptools
What it is and what it does
coherent-licensed is a Setuptools plugin designed to automate license file management during the Python package build process. It reads the License Expression declared in a package's metadata and automatically generates and injects the corresponding license file into the build artifacts, eliminating manual license file management.
The plugin is specifically built for coherent.build and skeleton projects. It operates only during builds and should not be installed to shared environments except temporarily; if it is, it emits a warning that can be suppressed via the COHERENT_LICENSED_UNUSED_ACTION environment variable. It has no runtime dependencies and requires Python 3.9 or later.
Use it for
- Automatically inject license files into Python packages during CI/CD builds to ensure license compliance
- Maintain consistency between declared License Expression and actual license files in build artifacts
- Reduce manual license file management in skeleton-based or coherent.build projects
- Ensure license declarations are reflected in distributed wheels and source distributions
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are building packages with coherent.build or skeleton and need automated license file injection.
Install only as a build requirement in your build-system configuration, not as a runtime or development dependency. The low friction and active maintenance make it safe for this specific use case.
Install
coherent-licensed on PyPI
Before you install
Low install friction with no runtime dependencies. Active maintenance as of July 2026. Intended only as a temporary build requirement; installing to a shared environment triggers a warning unless explicitly suppressed via environment variable.
Requires Python 3.9 or later. Intended for use during build only; not a runtime dependency.
License in practice
MIT license permits commercial and private use with minimal restrictions. Suitable for projects with permissive licensing requirements.
Quickstart
# Install as build requirement in pyproject.toml
[build-system]
requires = ["setuptools", "coherent-licensed"]
# The plugin activates automatically during build
# License file is injected based on License Expression in metadataVerify before relying
- How the plugin determines which license file format or location to use when injecting
- Whether the plugin works with all License Expression formats or has limitations
- Integration compatibility with build backends other than Setuptools
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release >=3.9 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Actively maintained 438 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 120,872 / month, #12,005 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 4 - BetaIntended Audience :: DevelopersProgramming Language :: Python :: 3Programming Language :: Python :: 3 :: Only |
Evidence: coherent_licensed-0.5.2-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “setuptools license injection plugin”
- coherent.licensedA Setuptools plugin that automatically injects a license file into…
- versioningitAutomatically determines your Python package's version from Git or…
- IncrementalIncremental is a CalVer version manager that automates version…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also setuptools-dso · pbr · conda-inject · versioneer-518 · snakemake-interface-report-plugins · poetry-plugin-shell · setuptools-odoo · mkdocs-markdownextradata-plugin · runtime-builder · pip-licenses