hgt-site
hgt-site finds places where DNA from bacteria or other organisms may have been inserted into a host genome, such as a human genome, using sequencing data. Most bacterial reads in these samples come from contamination or from DNA fragments joined by chance in the lab, so hgt-site checks each possible site against what chance alone would produce and keeps only the sites with clearly more support.
It takes paired-end reads aligned to the host (BAM, CRAM or SAM) and Kraken2 classifications of the reads that did not align, and writes a table of candidate sites, with optional BED, VCF and MultiQC files. Where reads cross the junction itself, the insertion point is given to the base pair. It works with any host alignment and Kraken2 output, including the files produced by nf-core/hgtseq.
In benchmarks on real human and bacterial genomes with added contamination, hgt-site reported no false sites across 18 runs on fresh random seeds. It is also fast: on a sample of 2.1 million reads it took about 3 seconds once the reads were aligned and classified, against about 2.5 minutes for LGTSeek.
Installation
pip install hgt-site
Usage
hgt-site run \
--bam sample.bam \
--kraken-db /path/to/kraken2-db \
--host-taxid 9606 \
--threads 8 \
-o sample.hgt-site.tsv \
--bed sample.hgt-site.bed \
--vcf sample.hgt-site.vcf
This classifies the unmapped reads with Kraken2 and calls the sites in one step, and needs kraken2 on PATH. If the reads have already been classified, use hgt-site call --kraken sample.kraken2.txt instead, which accepts several files at once.
To try it on simulated data with known insertion sites:
hgt-site simulate -o demo
hgt-site call --bam demo.sam --kraken demo.kraken2.txt --host-taxid 9606 -o demo.tsv
Documentation and benchmarks
Full documentation: https://iraajgangavaram.github.io/hgt-site/
Source code, benchmark scripts and results: https://github.com/iraajgangavaram/hgt-site
Citation
If you use hgt-site, please cite it: https://doi.org/10.5281/zenodo.23842712
Licence
MIT
Metadata
Release files for hgt-site 0.3.0
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 | Actions |
|---|---|---|---|---|
| hgt_site-0.3.0.tar.gz | 39.3 kB | With provenance | Details for hgt_site-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hgt_site-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for hgt_site-0.3.0-py3-none-any.whl |
Total release size: 66.3 kB
Release files / hgt_site-0.3.0.tar.gz
| Download URL | hgt_site-0.3.0.tar.gz |
|---|---|
| Size | 39.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1dec5c021625d183ffe4206fbf1d75d39da824903118fd85af9b1e2610ae7c5f
|
|
BLAKE2b-256 checksum How to use checksums |
b5fd1e0c2dd3635dbb87ffbd0d7bb7bf4bd5535de710005444d0aa02891f8f5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logRelease files / hgt_site-0.3.0-py3-none-any.whl
| Download URL | hgt_site-0.3.0-py3-none-any.whl |
|---|---|
| Size | 27.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
912f28e0cfe689e57b532fd3a42420b1839669d6a86066c4611dce555075ee4e
|
|
BLAKE2b-256 checksum How to use checksums |
0ddbc3a1ce745d0096b2dd79111dd9d2048c017525cef6af81feae51278468a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logSecurity for hgt-site 0.3.0
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 hgt_site-0.3.0.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 Nov 2, 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.