fhr (renamed to fair-bioheaders)
The fhr package on PyPI is now
fair-bioheaders, developed at
FAIR-bioHeaders-Tools.
This fhr distribution contains no code. It requires the same version of
fair-bioheaders, so pip install fhr and pip install -U fhr keep installing
the tools. For new installs and requirements, use fair-bioheaders directly:
python -m pip install fair-bioheaders
Everything that worked with fhr 0.3 keeps working:
- The
fhr-convert,fhr-validate,fhr-fasta-*, andfhr-gfa-*commands are unchanged. The newbioheaderscommand offers the same operations as subcommands (bioheaders convert,validate,combine,strip,verify). import fhrandfrom fhr.cli import ...still work but emit aDeprecationWarning; useimport bioheadersandbioheaders.cliinstead.
This distribution also declares the fhr-* commands, so that upgrading from
fhr 0.3 with pip keeps them. If you later uninstall fhr, restore them with:
python -m pip install --force-reinstall --no-deps fair-bioheaders
In an environment that still has fhr 0.3, uninstall it before installing
fair-bioheaders on its own, or upgrade with python -m pip install -U fhr.
See the changelog for details.
Metadata
Release files for fhr 0.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fhr-0.8.1.tar.gz | 18.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fhr-0.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.8 kB
Release files / fhr-0.8.1.tar.gz
| Download URL | fhr-0.8.1.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
067c4247833d245a968e85dec16763b17a805645695642cb42fbb09efa59c721
|
|
BLAKE2b-256 checksum How to use checksums |
248693183f93af502f9fbd635cfaf33cbdbd4104e21ac4c2eae5050d11f18399
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / fhr-0.8.1-py3-none-any.whl
| Download URL | fhr-0.8.1-py3-none-any.whl |
|---|---|
| Size | 16.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7e1a350c5463cd77e6d5e983b807ad4ccd9852d392354f884bd3f448360f7de
|
|
BLAKE2b-256 checksum How to use checksums |
ec10221b9db7f10fb5d003e14f1ba3952f119192488462e4c35ea3066599aac3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for fhr 0.8.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for fhr-0.8.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.