NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI
PyPI, #2046 most downloaded on PyPI
Dump the software license list of Python packages installed with pip.
Latest stable
5.5.5
Last release 13 days ago
09 Nov 2026
Release timing varies
gaps range from 2 weeks to 1.2 years
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
78 releases · first in 2018
Drag across the ruler to compare, or tap a release to open it.
> This pre-release includes important developer security fixes, and supersedes previous _v6-series betas_.
<details><summary>Also pushes last BETA v6.0.0b14 to default branch for release.</summary>
Patch Notes for v6.0.0 Beta Candidate (
v6.0.0b14)This pre-release will end the
beta-phase of development onpip-licenses v6. _remaining work before the release ofv6.0.0proper will focus on custodial improvements (documentation, stability, and perhaps some polishing).v6.0.0is currently on-track for release before the coming new year.Note
Want to prepare to migrate early?
A living Migration-Guide draft is now available On the github project wiki Note
This will also, be an opt-in pre-release (via
pip install --pre ...(but is intended to supersede the LTS v5.5.5) A few things may need to change before the final v6 release (e.g., break-fixes, exact wording of diagnostics, etc.). See Version 6.x Series and #349 for more. This pre-release includes important developer security fixes, and supersedes previous v6-series betas.Impacted GHIs
Contributes to work on v6 series changes/migration Document #349
- [x] Resolves/Closed related finalize v6 series formatting argument precedence #375
[x] Resolves/Closed Import error running
6.0.0b11#384
- [x] Resolves/Closed related CHORE: new test scenario for distribution archive contents #265
[x] Resolves/Closed [CHORE] Fix prototype for docker builds in CI/CD #387
[x] Resolves/Closed [CHORE] Resolve Regression in output-file support due to incomplete work on GHI-375 #389
[x] Resolves/Closed Wire-up
--warn-onCLI flag #411
- Contributes to work on related Fix case for
--from=mixedwhen license expression is present && other values are too. #414 (remains unresolved)[x] Resolves/Closed --ignore-package with a version spec does not match the metadata's own version spelling #423
[x] Resolves/Closed Warn when no packages are found #426
[x] Resolves/Closed Chore: CI regression for python3.9 on Ubuntu 26 due to GHA runners migrating #434
Contributes to work on Chore: resolve Dependabot
allowversusignoreconfiguration rules conflict #435Included & Superseded PR/MRs
- Includes & Supersedes Pre-Release Candidate for
v6.0.0b13#385 (v6.0.0b13) and related- Includes & Supersedes Implement planned changes to CLI flags and a clear migration path #391 and related
- Supersedes Bump virtualenv from 21.2.0 to 21.14.13 #419
- Supersedes Bump certifi from 2026.2.25 to 2026.10.19 #420
- Includes & Supersedes [FEATURE] added validation logic to CLI parsing #421
- Includes [PATCH] Warn when no packages are found (GHI #426) #427
- Includes & Supersedes [PATCH] Restore Dependabot updates for allowed Python dependencies #429
- Supersedes [PATCH] Bump pypi-publish to v1.14.3 (GHSA-5xjx-3w67-w9x9) #430
Acknowledgments
🎉 Special thanks to the following:
- @rahul05ranjan for their work implementing Wire-up
--warn-onCLI flag #411- @yprez for their work implementing Warn when no packages are found #426
- @andife for submitting PRs [PATCH] Restore Dependabot updates for allowed Python dependencies #429 & [PATCH] Bump pypi-publish to v1.14.3 (GHSA-5xjx-3w67-w9x9) #430
Migration Notes
- see v6 series changes/migration Document #349 for status on the migration document/guide
Important
Several legacy v6 CLI/config keys are still accepted for compatibility, but some forms are now marked as deprecated and may emit warnings. The canonical behavior is now more explicit and standardized around the with/without and global file/path toggles.
- Legacy single-form flags such as
--no-license-pathand--no-file-pathsare still accepted for migration compatibility, but their behavior is normalized through the newer path toggle model.--with-license-files,--with-notice-files,--with-other-files, and their path toggles are now handled more consistently across parsing and output rendering.- Config values that were serialized as semi-colon-delimited lists are parsed more carefully to preserve intended escaping semantics.
- If you pass an
output_fileprogrammatically (remains unsupported; see Calling from within Python #81), ensure it is a path string; non-string-like values are now normalized more defensively before write attempts.
</details>
v6.0.0b14) - (Early migration release) by @reactive-firewall in https://github.com/raimon49/pip-licenses/pull/392Full Changelog: https://github.com/raimon49/pip-licenses/compare/v-6.0.0b13...v-6.0.0b14
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Patch Notes for v6.0.0 Beta Candidate (
v6.0.0b14)This pre-release will end the
beta-phase of development onpip-licenses v6. _remaining work before the release ofv6.0.0proper will focus on custodial improvements (documentation, stability, and perhaps some polishing).v6.0.0is currently on-track for release before the coming new year.Note
Want to prepare to migrate early?
A living Migration-Guide draft is now available On the github project wiki
NoteThis will also, be an opt-in pre-release (via
pip install --pre ...(but is intended to supersede the LTS v5.5.5) A few things may need to change before the final v6 release (e.g., break-fixes, exact wording of diagnostics, etc.). See Version 6.x Series and #349 for more.
This pre-release includes important developer security fixes, and supersedes previous v6-series betas.Impacted GHIs
Contributes to work on v6 series changes/migration Document #349
- Resolves/Closed related finalize v6 series formatting argument precedence #375
Resolves/Closed Import error running
6.0.0b11#384
- Resolves/Closed related CHORE: new test scenario for distribution archive contents #265
Resolves/Closed [CHORE] Fix prototype for docker builds in CI/CD #387
Resolves/Closed [CHORE] Resolve Regression in output-file support due to incomplete work on GHI-375 #389
Resolves/Closed Wire-up
--warn-onCLI flag #411
- Contributes to work on related Fix case for
--from=mixedwhen license expression is present && other values are too. #414 (remains unresolved)Resolves/Closed --ignore-package with a version spec does not match the metadata's own version spelling #423
Resolves/Closed Warn when no packages are found #426
Resolves/Closed Chore: CI regression for python3.9 on Ubuntu 26 due to GHA runners migrating #434
Contributes to work on Chore: resolve Dependabot
allowversusignoreconfiguration rules conflict #435Included & Superseded PR/MRs
- Includes & Supersedes Pre-Release Candidate for
v6.0.0b13#385 (v6.0.0b13) and related- Includes & Supersedes Implement planned changes to CLI flags and a clear migration path #391 and related
- Supersedes Bump virtualenv from 21.2.0 to 21.14.13 #419
- Supersedes Bump certifi from 2026.2.25 to 2026.10.19 #420
- Includes & Supersedes [FEATURE] added validation logic to CLI parsing #421
- Includes [PATCH] Warn when no packages are found (GHI #426) #427
- Includes & Supersedes [PATCH] Restore Dependabot updates for allowed Python dependencies #429
- Supersedes [PATCH] Bump pypi-publish to v1.14.3 (GHSA-5xjx-3w67-w9x9) #430
Acknowledgments
🎉 Special thanks to the following:
- @rahul05ranjan for their work implementing Wire-up
--warn-onCLI flag #411- @yprez for their work implementing Warn when no packages are found #426
- @andife for submitting PRs [PATCH] Restore Dependabot updates for allowed Python dependencies #429 & [PATCH] Bump pypi-publish to v1.14.3 (GHSA-5xjx-3w67-w9x9) #430
Migration Notes
- see v6 series changes/migration Document #349 for status on the migration document/guide
Important
Several legacy v6 CLI/config keys are still accepted for compatibility, but some forms are now marked as deprecated and may emit warnings. The canonical behavior is now more explicit and standardized around the with/without and global file/path toggles.
- Legacy single-form flags such as
--no-license-pathand--no-file-pathsare still accepted for migration compatibility, but their behavior is normalized through the newer path toggle model.--with-license-files,--with-notice-files,--with-other-files, and their path toggles are now handled more consistently across parsing and output rendering.- Config values that were serialized as semi-colon-delimited lists are parsed more carefully to preserve intended escaping semantics.
- If you pass an
output_fileprogrammatically (remains unsupported; see Calling from within Python #81), ensure it is a path string; non-string-like values are now normalized more defensively before write attempts.
v6.0.0b14) - (Early migration release) by @reactive-firewall in #392Full Changelog: v-6.0.0b13...v-6.0.0b14
Fixed a deprecation/regression path around mixed-source license discovery and ordering logic for multi-source results.
v6.0.0b13)A third peek at some of the big changes coming in pip-licenses v6.
[!NOTE] This will also, be an opt-in pre-release (via
pip install --pre ...(and does not supersede the LTS v5.5.5 yet) A few things are going to change before the final v6 release. See Version 6.x Series for planned work.
Contributes to work on #71 (Ready for user feedback)
<details><summary>And Related</summary>
</details>
Contributes to work on #81 (W.I.P.)
This beta release improves build validation, packaging stability, and Docker release automation while continuing the v6 migration toward a more modular, metadata-aware, and documentation-driven experience. It adds new include/exclude-style flags, better example coverage, and stronger CI validation for the upcoming stable v6 release.
Highlights:
What’s new
Beta build reliability improvements
New and updated CLI options
Output and metadata improvements
Documentation improvements
Release engineering and CI improvements
Dependency and project hygiene
Fixes and hardening
Documentation and migration notes
Compatibility notes
Notable package and release changes
Potential impact for users
[!NOTE] This is a beta release. All features and APIs are subject to change before the final 6.0.0 release.
Full Changelog: https://github.com/raimon49/pip-licenses/compare/v-6.0.0a1...v-6.0.0b13
Aligned with PEP-749 (formerly PEP-753) regarding typing.TYPE_CHECKING deprecation
v6.0.0b11)A second peek at some of the big changes coming in pip-licenses v6.
[!CAUTION] This pre-release was discovered to have issues and should be avoided (see #384). (LTS v5.5.5 remains the latest stable release)
[!NOTE] This will also, be an opt-in pre-release (via
pip install --pre ...(and does not supersede the LTS v5.5.5 yet) A few things are going to change before the final v6 release. See Version 6.x Series for planned work.
Contributes to work on #71 (W.I.P.)
<details><summary>And Related</summary>
</details>
Contributes to work on #81 (W.I.P.)
piplicenses.py has been split into a modular package with organized submodules:
piplicenses/__init__.py - Main package entry pointpiplicenses/__main__.py - CLI entry pointpiplicenses/cli/ - Command-line argument parsing and configurationpiplicenses/core.py - Core license discovery logicpiplicenses/output/ - Output formatting (tables, JSON, CSV, HTML, etc.)piplicenses/sorting.py - License comparison and filtering utilitiespiplicenses/constants.py - Centralized constants and field definitionspiplicenses/tomli_bridge.py - TOML file handling shimConfiguration object for better type safety and IDE supportpiplicenses.main() entry point moved to piplicenses.__main__.main()--with-license-file → --with-license-files (plural form added)--with-notice-file → --with-notice-files (plural form added)--no-version → --without-version (standardized naming)--no-license-path → --without-license-paths (standardized naming)--with-other-files - Include other licensing-related files--no-file-paths - Suppress all file path outputs--format=expression - Support for PEP-639 license expressionstyping.TYPE_CHECKING deprecationextract_urls() function for comprehensive Project-URL parsinghome-page metadata field for compatibility--with-license-files flag for extracting all license files<thead> and <tbody> tagsmake local-ci-check target for pre-push validationactions/checkout@v7.0.0 (from v6.0.2)actions/attest@v4.1.1 (from v4.1.0)codecov/codecov-action@v7.0.0 (from v6.0.0)actions/upload-artifact@v7.0.1 (from v7.0.0)twine from development dependencies (simplified build process)mypy==1.19.1 for Python 3.9 supportpyproject.toml structure for modern Python packaging standards[!NOTE] This is a beta release. All features and APIs are subject to change before the final 6.0.0 release.
Full Changelog: https://github.com/raimon49/pip-licenses/compare/v-6.0.0a1...v-6.0.0b11
v6.0.0b11)A second peek at some of the big changes coming in pip-licenses v6.
Note
This will also, be an opt-in pre-release (via pip install --pre ... (and does not supersede the LTS v5.5.5 yet) A few things are going to change before the final v6 release. See Version 6.x Series for planned work.
piplicenses.py has been split into a modular package with organized submodules:
piplicenses/__init__.py - Main package entry pointpiplicenses/__main__.py - CLI entry pointpiplicenses/cli/ - Command-line argument parsing and configurationpiplicenses/core.py - Core license discovery logicpiplicenses/output/ - Output formatting (tables, JSON, CSV, HTML, etc.)piplicenses/sorting.py - License comparison and filtering utilitiespiplicenses/constants.py - Centralized constants and field definitionspiplicenses/tomli_bridge.py - TOML file handling shimConfiguration object for better type safety and IDE supportpiplicenses.main() entry point moved to piplicenses.__main__.main()--with-license-file → --with-license-files (plural form added)--with-notice-file → --with-notice-files (plural form added)--no-version → --without-version (standardized naming)--no-license-path → --without-license-paths (standardized naming)--with-other-files - Include other licensing-related files--no-file-paths - Suppress all file path outputs--format=expression - Support for PEP-639 license expressionstyping.TYPE_CHECKING deprecationextract_urls() function for comprehensive Project-URL parsinghome-page metadata field for compatibility--with-license-files flag for extracting all license files<thead> and <tbody> tagsmake local-ci-check target for pre-push validationactions/checkout@v7.0.0 (from v6.0.2)actions/attest@v4.1.1 (from v4.1.0)codecov/codecov-action@v7.0.0 (from v6.0.0)actions/upload-artifact@v7.0.1 (from v7.0.0)twine from development dependencies (simplified build process)mypy==1.19.1 for Python 3.9 supportpyproject.toml structure for modern Python packaging standardsNote
This is a beta release. All features and APIs are subject to change before the final 6.0.0 release.
Full Changelog: v-6.0.0a1...v-6.0.0b11
6.0.0b11 (BROKEN) Pre-release
Pre-release
Compare
Multiple Development (v6 betas) re-joined by @reactive-firewall in https://github.com/raimon49/pip-licenses/pull/361
Full Changelog: https://github.com/raimon49/pip-licenses/compare/v-6.0.0a1...v-6.0.0b10
Full Changelog: v-6.0.0a1...v-6.0.0b10
> pip-licenses was *NOT* impacted by CVE-2025-47273. pip install pip-licenses>=5 will _not_ have install the affected package setuptools<78.1.1 (despi…
A sneak peek at some of the changes coming in pip-licenses v6 and some minor documentation corrections.
[!NOTE] This will be an opt-in pre-release (via
pip install --pre ...(and does not supersede the LTS v5.5.5)
Include with this release is a preview of the next LTS container version via, a long overdue, updated Dockerfile
[!IMPORTANT]
pip-licenseswas NOT impacted by CVE-2025-47273.pip install pip-licenses>=5will not have install the affected packagesetuptools<78.1.1(despite an outdated example in the README.md); Most users should have been unaffected (except possibly on outdated forks?) unless doing very strange (unsupported) things withpip-licenses's source builds like monkey-patching the build logic, then maybe :hear_no_evil:.
Numerous examples throughout the README.md (which is included in the official distributions, and may worry your favorite security tools) have been updated thanks to work by @matejkloska :tada:
[!IMPORTANT]
pip-licenseswas NOT impacted by CVE-2026-4539 for normal use-cases.pip install pip-licenses>=5will not install the affected developer packagePypgments; Most users should have been unaffected (except possibly on forked projects).
Fixed false positive of: CVE-2026-4539 reDoS. Removed optional (and historical) use of twine to fix alert.
[!IMPORTANT] Furthermore,
pip-licenseswas NOT impacted by CVE-2026-44432. Furthermore,pip-licenseswas NOT impacted by CVE-2026-44431.
Fixed false positive of CVE-2026-44432. Removed optional (and historical) use of twine to fix alerts.
Fixed false positive of CVE-2026-44431.
[!IMPORTANT] :construction: Upgrades are in-progress, please pardon the noisy changes and dust.
--with-*-files (as originally suggested by @johnthagen) plural nomenclature (~file~ vs files) will lead to a more intuitive usage - these will be formally introduced in a future stable release (but this is an early sneak peek currently based on work by @stefan6419846)These initial new flags are currently implemented in a purely stop-gap form (as they are based on the PR stefan6419846/pip-licenses-cli#132 (which was originally a fix for stefan6419846/pip-licenses-cli#8 that @johnthagen is similar to raimon49/pip-licenses#71 and #242). To completely fix GHI #71 and related, full support of multiple licenses for a single package will become the default. This seemingly small design change will have impacts throughout the entire codebase. But for most users this hopefully will just look like adding an s to the --with-license-file flag (and the plan is to replace the old flag mostly behind the scenes to minimize potential breaking changes) or even no change to usage just a noisy depreciation warning that can be ignored (this re-design is not really about removing any features)
So yeah this would-be the next v5.5.x if not for all that; hence the bump to v6 (alpha))
<details><summary>and related...</summary>
</details>
Full Changelog: https://github.com/raimon49/pip-licenses/compare/v-5.5.5...v-6.0.0a1
A sneak peek at some of the changes coming in pip-licenses v6 and some minor documentation corrections.
Note
This will be an opt-in pre-release (via pip install --pre ... (and does not supersede the LTS v5.5.5)
Include with this release is a preview of the next LTS container version via, a long overdue, updated Dockerfile
Important
pip-licenses was NOT impacted by CVE-2025-47273. pip install pip-licenses>=5 will not have install the affected package setuptools<78.1.1 (despite an outdated example in the README.md); Most users should have been unaffected (except possibly on outdated forks?) unless doing very strange (unsupported) things with pip-licenses's source builds like monkey-patching the build logic, then maybe 🙉.
Numerous examples throughout the README.md (which is included in the official distributions, and may worry your favorite security tools) have been updated thanks to work by @matejkloska 🎉
Important
pip-licenses was NOT impacted by CVE-2026-4539 for normal use-cases. pip install pip-licenses>=5 will not install the affected developer package Pypgments; Most users should have been unaffected (except possibly on forked projects).
Fixed false positive of: CVE-2026-4539 reDoS. Removed optional (and historical) use of twine to fix alert.
Important
Furthermore, pip-licenses was NOT impacted by CVE-2026-44432.
Furthermore, pip-licenses was NOT impacted by CVE-2026-44431.
Fixed false positive of CVE-2026-44432. Removed optional (and historical) use of twine to fix alerts.
Fixed false positive of CVE-2026-44431.
Important
🚧 Upgrades are in-progress, please pardon the noisy changes and dust.
--with-*-files (as originally suggested by @johnthagen) plural nomenclature (These initial new flags are currently implemented in a purely stop-gap form (as they are based on the PR stefan6419846/pip-licenses-cli#132 (which was originally a fix for stefan6419846/pip-licenses-cli#8 that @johnthagen is similar to #71 and #242). To completely fix GHI #71 and related, full support of multiple licenses for a single package will become the default. This seemingly small design change will have impacts throughout the entire codebase. But for most users this hopefully will just look like adding an s to the --with-license-file flag (and the plan is to replace the old flag mostly behind the scenes to minimize potential breaking changes) or even no change to usage just a noisy depreciation warning that can be ignored (this re-design is not really about removing any features)
So yeah this would-be the next v5.5.x if not for all that; hence the bump to v6 (alpha))
Full Changelog: v-5.5.5...v-6.0.0a1
Combines recent pre-releases (including 5.5.2-5.5.4) to deliver significant codebase cleanup and lays the groundwork for upcoming changes planned for
Combines recent pre-releases (including 5.5.2-5.5.4) to deliver significant codebase cleanup and lays the groundwork for upcoming changes planned for version v6.0.
Full Changelog: https://github.com/raimon49/pip-licenses/compare/v-5.5.4...v-5.5.5
> This is an early pre-release to bring the default branch closer to upcoming development changes.
[!IMPORTANT] PRE-RELEASE UPDATE This is an early pre-release to bring the default branch closer to upcoming development changes.
~Fixes #288. See GHI #288 & PR #313 for more info and relevant discussion.~
prek~
pre-commit-config.yaml based on work by @DimitriPapadopoulos~ruff configurations
ruff rules for style a more black compatible experiencerufffilelock dependency across python versionsMakefile for developer workflowsprek/pre-commit for CI linting and local developer workflowsrequires-python remains >=3.9 (note: CI deprecates 3.9 for black)
Contains packaging and CI updates, dependency/dev-dependency security updates, small code/style fixes (typos, formatting), and preparation for PEP-compliant metadata and sdist behaviour.
setuptools-scm (avoid duplicative explicit include lists).piplicenses.py — version bump, docstring typo fix, style/formatting adjustments CHANGELOG.md — added 5.5.1 notes pyproject.toml — PEP-639/753 packaging metadata and URL label normalisation MANIFEST.in — adapted for setuptools-scm (prune/exclude) dev-requirements.txt — urllib3, wheel updates .github/workflows/python-package.yml and .github/workflows/CD-PyPi.yml — updated action references, black job conditional, upload/download artifact and codecov action upgrades
Full Changelog: https://github.com/raimon49/pip-licenses/compare/v-5.5.0...v-5.5.1
pyproject.toml with PEP 753pyproject.toml (e.g., packaging metadata) into alignment with PEP 639 and related packaging guidance.
MANIFEST.in to setuptools-scm build logic with better filtering, closing GHI #266black by deprecating support for python 3.9, closing GHI #264
black 26.1.0suggestions to codebase, closing GHI #269Initial Implementation of PEP-639 support
tomllib for Python 3.11+ (reducing external dependencies by 1)tomli with builtin tomllib for Python 3.11License-Expression metadata field, see PEP 639--from=expression option--from=all output now includes the License-Expression value--partial and --allow-only if a license matches multiple allowed licenses.--with-license-file option in documentationClarified support for Python 3.12
Fixes "tomli" to be output only with --with-system option
--with-system optionImplement new feature pyproject.toml support
Implement new option --partial-match
--partial-matchMaintain to pass test with wcwidth>=0.2.10
Always terminate --allow-only and --fail-on messages with a newline
--allow-only and --fail-on messages with a newline--output-file with a newlineBetter handling extracting URLs from Project-URL
Project-URLFix to treat package names as normalized as in PEP 503 with --packages and --ignore-packages option
--packages and --ignore-packages optionImplement new option --no-version
--no-versionImplement new option --with-maintainers
--with-maintainers--python--ignore-packages parametersAuthor field is UNKNOWN, the output is automatically completed from Author-emailhome-page field is UNKNOWN, the output is automatically completed from Project-URLNothing published for this version
Nothing published for this version
Nothing published for this version
Support case-insensitive license name matching around --fail-on and --allow-only parameters
--fail-on and --allow-only parametersEscape unicode output (to e.g. {) in the html output
{) in the html outputAdd type annotations and code formatter
Fix "pip-licenses" is missing in output of pip-licenses --with-system option
pip-licenses --with-system optionMigrate Docker base image from Alpine to Debian 11-slim
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Search for path defined in PEP 639
--with-license-file optionSkip directories when detecting license files
* Support pip 21.3 or later
Ignore spaces around --fail-on and --allow-only parameters
--fail-on and --allow-only parametersFix the order in which multiple licenses are output
Handle multiple licenses better with options --fail-on and --allow-only
--fail-on and --allow-onlyPython Software Foundation License, MIT LicensePython Software Foundation License; MIT LicenseImplement new option --packages
--packagesNothing published for this version
Fix license summary refer to --from option
--from optionImproves the readability of the help command
Implement new option --from=all
--from=allImplement new option for use in continuous integration
--fail-on--allow-onlyClarified support for Python 3.9
setup.cfg--from=mixedImplement new option for manage unicode characters
--filter-strings--filter-code-pageFixed the file that is selected when multiple matches are made with LICENSE* with run --with-license-file
LICENSE* with run --with-license-fileImplement new option --with-notice-file
--with-notice-fileLICENCE with run --with-license-fileSuppress errors when opening license files
Implement new option --format=plain-vertical
--format=plain-verticalCOPYING *Better license file open handling in Python 3
Removed migration path to obsolete options
--from-classifier--format-markdown--format-rst--format-confluence--format-html--format-json--no-license-pathSupports compatibility to work with either PTable or prettytable
Implement new option --output-file
--output-fileAdd a help text for --format=json-license-finder option
--format=json-license-finder optionImplement new option --format=json-license-finder
--format=json-license-finderRead license file works well with Windows
Skip parsing of license file for packages specified with --ignore-packages option
--ignore-packages optionImplement new option --format=csv
--format=csvImplement new option --from=mixed as a mixed mode
--from=mixed as a mixed modeImplement new option --from=meta, from=classifier
--from=meta, from=classifierOne column per quarter.