Skip to main content

UnifyVcf

Unifies the separate structural call files a sequencing pipeline produces into the single VCF Geneyx reads as an SV VCF.

The files it unifies are:

  • SV – structural variants VCF
  • CNV – copy number variants VCF
  • Repeats – tandem repeat variants VCF
  • ROH – Regions of Homozygosity (DRAGEN BED, or an already-converted VCF)

It does not only concatenate them. Each caller writes slightly different files, and Geneyx needs specific fields to read a record properly — so records are rewritten on the way out and the result is sorted and bgzipped. Run the entry point that matches the pipeline your VCFs came from.

This package is the single implementation behind both the customer-facing scripts in geneyx.analysis.api and the Geneyx primary pipeline, so both produce the same unified file.

Installation

pip install UnifyVcf

Python 3.9–3.13 on Linux, macOS or Windows, with no external tools required and no dependencies outside the standard library. Sorting and BGZF compression are pure Python; repeat filtering uses bedtools when it is installed and computes the same intersection itself when it is not.

Wheels are published per platform and Python version because the implementation ships compiled — see How this is distributed. If pip install reports no matching distribution, your platform or Python version is outside the published set; tell us which and we will add it.

Command line

dragen-unify-vcf  -o OUTPUTPATH [-s SVPATH] [-c CNVPATH] [-r REPEATPATH] [-d ROH_BED_FILE]
ont-unify-vcf     -o OUTPUTPATH [-s SVPATH] [-c CNVPATH] [-r REPEATPATH] [-modify]
pacbio-unify-vcf  -o OUTPUTPATH [-s SVPATH] [-c CNVPATH] [-r FULLREPEATPATH] [-b REPEATLOCATIONSBEDFILEPATH]
Argument Meaning
-o Path to the unified VCF, including its name. The output is compressed, so the name should end in .vcf, not .gz.
-s Structural variants (SV) VCF. Gzipped or not.
-c Copy number variants (CNV) VCF. Gzipped or not.
-r Tandem repeats VCF. Gzipped or not.
-d DRAGEN only. The ROH BED produced by DRAGEN when run with --vc-enable-roh.
-modify ONT only, and no longer needed. Forces ;SVTYPE=REP onto every repeat call. Without it, a repeat call that carries no SVTYPE is marked anyway and one that already has one is left alone.
-b PacBio only. A BED restricting which repeat loci are unified. Without -b the repeats are left out of the unified file entirely, because the full TRGT catalog is far wider than a report can interpret.

A catalog of pathogenic hg38 STR loci ships with the package:

from UnifyVcf import default_repeat_catalog_path
pacbio-unify-vcf -o unified.vcf -s sv.vcf.gz \
  -r sample.GRCh38.trgt.sorted.vcf.gz \
  -b "$(python -c 'from UnifyVcf import default_repeat_catalog_path as p; print(p())')"

Python

from UnifyVcf import run

run(output_path="unified.vcf", sv_path="sv.vcf.gz", cnv_path="cnv.vcf.gz",
    repeat_path="repeats.vcf.gz", roh_bed_path="roh.bed")

run keeps the signature the standalone UnifyVcf.py script published, so code that did from UnifyVcf import run works unchanged once this package is installed.

A caller that already owns a sorting step — the Geneyx pipeline does — skips run and composes the pieces instead, so it keeps its own sorting and indexing:

from UnifyVcf import UnifyOptions, read_struct_lines, unify_lines

options = UnifyOptions(drop_sv_filters=("InvBreakpoint",))  # exclude by FILTER
unify_lines(read_struct_lines(paths, options), "unified.vcf", options)   # unsorted

Nothing about the shape of the inputs has to be declared. Whether a repeat record needs ;SVTYPE=REP is read off the record, and whether ROH arrived as a BED or an already-converted VCF is read off the file — so the same call is correct for DRAGEN, ONT and PacBio input. UnifyOptions still accepts add_repeat_svtype and roh_format as overrides for a caller that knows better than its files do.

How the pieces fit

Function Does
read_struct_lines(paths, options) Reads each input (gzipped or not), drops excluded SV records, and skips inputs that are empty or header-only.
unify_lines(lines, output_path, options) Writes the unified, unsorted VCF. Returns None when there was nothing to write.
sort_and_compress(vcf_path) Sorts by position and bgzips; returns the .gz path.
filter_repeats_vcf(repeat_path, bed_path) Intersects a repeat VCF with a locus catalog, via bedtools or in Python.

PacBio has two front doors over these, because repeat filtering is separable: pacbio_filter_and_unify filters the full TRGT VCF against a catalog and then unifies, which is what pacbio-unify-vcf runs; pacbio_unify unifies repeats that are already filtered, for a caller that owns that step itself.

The first present input in SV → CNV → repeats order donates the header; the rest contribute records only.

Platform support

Everything runs on Linux, macOS and Windows. Two things used to be Linux-only and are no longer:

Sorting and compression. The output has to be sorted by position and compressed as BGZF — a gzip variant written in <64KB blocks — because Geneyx indexes it with tabix, and tabix cannot index plain gzip. Compression is always pure Python. Sorting has two engines: a pure-Python one that needs no sort binary, and one that shells out to a real sort -k1,1 -k2,2n — several times faster past a few hundred thousand records, which a PacBio long-read callset can reach. sort_and_compress prefers the sort binary when it is on PATH, the same way repeat filtering below prefers bedtools. Either way the ordering matches what sort -k1,1 -k2,2n produced under the previous shell implementation, including GNU sort's whole-line tie-break, so files keep the order Geneyx has always received — tests/test_sort_parity.py pins the two engines against each other to prove it.

Repeat filtering. bedtools intersect is used where bedtools is on PATH. Where it is not, the same intersection is computed in Python: a record spans [POS-1, END), taking END from INFO where present — repeat callers emit symbolic <STR> alleles whose length is not the length of REF — and falling back to POS-1 + len(REF). The engine that ran is logged. The CI runs the suite on both Linux and Windows, and the Linux leg installs bedtools so the two engines are compared against each other rather than one being skipped.

Force one or the other when you need to:

from UnifyVcf import BEDTOOLS, BUILTIN, filter_repeats_vcf

filter_repeats_vcf(repeats, catalog, engine=BUILTIN)
from UnifyVcf import GNU_SORT, PYTHON_SORT, sort_and_compress

sort_and_compress(unified_vcf_path, engine=PYTHON_SORT)

How this is distributed

The wheel ships compiled modules (.pyd on Windows, .so elsewhere), not .py files. What it publishes instead is the interface:

  • UnifyVcf/*.pyi type stubs carrying every public signature and its description, generated from the source by tools/generate_stubs.py
  • the same docstrings inside the compiled modules, so help(UnifyVcf.run) works
  • py.typed, so mypy and IDEs read the stubs
  • this README

So autocomplete, type checking and help() behave normally; the function bodies are just not there to read. __init__.py stays interpreted deliberately — it is only re-exports, and it is the surface this README documents.

Consequences worth knowing:

  • No sdist is published. An sdist would carry the sources, undoing the point. pip download --no-binary :all: therefore has nothing to fetch.

  • One wheel per platform and Python version, built by cibuildwheel in CI, rather than the single pure-Python wheel a normal package gets.

  • Import from UnifyVcf, not from its submodules. Pylint will not import an extension module to see what it exports, and it does not read the stubs, so a perfectly good from UnifyVcf.cli import dragen_from_cli is reported as E0611: No name 'dragen_from_cli' in module 'UnifyVcf.cli'. __init__.py stays interpreted, so pylint reads the names straight out of it and from UnifyVcf import dragen_from_cli analyses cleanly — which is why everything public is re-exported there. A caller that does need a submodule directly wants this in its pylint config:

    [MAIN]
    extension-pkg-allow-list=UnifyVcf
    

    mypy and Pylance need neither, they read the stubs.

  • This is a deterrent, not a control. A compiled extension can still be analysed, and string literals — log messages, ;SVTYPE=REP and the like — remain visible in the binary because the code has to use them at run time. It stops casual reading and copy-paste reuse; it is not a security boundary.

Working on the package

The sources live in this repository and run interpreted, so development and the test suite are unaffected:

pip install -e .            # needs a C compiler; builds the extensions in place
python -m pytest tests
python tools/generate_stubs.py          # after changing any public signature
python tools/generate_stubs.py --check  # what CI enforces

tests/test_published_surface.py fails if a stub drifts from the source, so the published description cannot silently stop matching the code.

Per-caller differences

These are options rather than separate implementations:

DRAGEN ONT PacBio Geneyx pipeline
;SVTYPE=REP on repeats detected detected detected detected
ROH input detected – – detected
Repeat filtering – – bedtools against -b done as its own pipeline step
SV FILTER exclusions none none none InvBreakpoint (PacBio)

The first two rows used to be per-caller options and are now read off the files, so those callers no longer differ at all. The third is the same filter_repeats_vcf call on both sides, made at a different point — see the two PacBio front doors above.

The last row is a real difference and not one this package can resolve: a customer unifying their own PacBio VCFs keeps InvBreakpoint records, and the pipeline drops them, so the same SV callset yields a different reported call set depending on which path unified it. Whether a breakpoint half of an inversion is a reportable event is a product decision, and it is listed here to stay visible until it is made.

The PacBio row and the pipeline row differ on InvBreakpoint deliberately: the Geneyx pipeline drops those records from the unified file it analyses, and the customer-facing script does not. Aligning them would change what customers upload, so it is a product decision rather than a packaging one.

Known defect carried over

Pinned by a characterization test rather than fixed, so that packaging stayed a refactor. Worth its own change:

is_valid_line misses single-sample no-calls. The GT is read from the last tab-separated cell, which on a single-sample record still carries the trailing newline, so "./.\n" != "./." and the no-call is kept. Multi-sample records take the intended path. The neighbouring gt_index == '0' compares an int to a str and is never true.

Two other defects in the original shell-based sorter are gone as a consequence of rewriting it for Windows, rather than by choice:

  • It swallowed its own failures — a failed sort or bgzip was logged and execution continued, leaving an unsorted, uncompressed .vcf where the caller expected .vcf.gz. Failures now raise.
  • Its temp directory was vcf-temp in the current working directory, so two runs in one directory deleted each other's temp files. Temporary files are now written beside the output and removed in a finally.

Tests

pytest tests

No bedtools, bgzip or network needed — the suite is file manipulation only. One test compares the two repeat-filtering engines and skips where bedtools is not installed.

Metadata

Release files for UnifyVcf 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distributions (wheels)

Table of built distributions (wheels) for UnifyVcf 0.2.0
File Actions
unifyvcf-0.2.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for unifyvcf-0.2.0-cp313-cp313-win_amd64.whl
unifyvcf-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for unifyvcf-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details for unifyvcf-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl
unifyvcf-0.2.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for unifyvcf-0.2.0-cp312-cp312-win_amd64.whl
unifyvcf-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for unifyvcf-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details for unifyvcf-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl
unifyvcf-0.2.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for unifyvcf-0.2.0-cp311-cp311-win_amd64.whl
unifyvcf-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for unifyvcf-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details for unifyvcf-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl
unifyvcf-0.2.0-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for unifyvcf-0.2.0-cp310-cp310-win_amd64.whl
unifyvcf-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for unifyvcf-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.9+ x86-64 Details for unifyvcf-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl
unifyvcf-0.2.0-cp39-cp39-win_amd64.whl CPython 3.9 CPython 3.9 Windows x86-64 Details for unifyvcf-0.2.0-cp39-cp39-win_amd64.whl
unifyvcf-0.2.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.9 CPython 3.9 Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for unifyvcf-0.2.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
unifyvcf-0.2.0-cp39-cp39-macosx_10_9_x86_64.whl CPython 3.9 CPython 3.9 macOS 10.9+ x86-64 Details for unifyvcf-0.2.0-cp39-cp39-macosx_10_9_x86_64.whl

Total release size: 9.9 MB

Release files / unifyvcf-0.2.0-cp313-cp313-win_amd64.whl

Download URL unifyvcf-0.2.0-cp313-cp313-win_amd64.whl
Size 208.4 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
c9c13e0b44308e0211f34f4dd5a97b44b568c408645679b939cc9cf2add9c376
BLAKE2b-256 checksum
How to use checksums
1a85555abb8acb5c8361ce61e80fd0233b95b77682663b121ac3b0e0e06b6d03
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
72e1e67166d9a1e9bb2f43a0a739d13f68d5db84e495143ff74b16b3479e9d4f
BLAKE2b-256 checksum
How to use checksums
3e30b5571ab4db3b1d57c166b3e0883786a28750ffe52e76956ccd001f4ea55c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl

Download URL unifyvcf-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl
Size 243.6 kB
Tags CPython 3.13 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
807a687dec5f64ebd64b4d731baddbd6d1d47c8b2e2e9d3c523c0ea64040833c
BLAKE2b-256 checksum
How to use checksums
f58fd846c2b3733ed26bf869d1a1ffdb8b8a21e61751a4b939d53aa31822bc60
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp312-cp312-win_amd64.whl

Download URL unifyvcf-0.2.0-cp312-cp312-win_amd64.whl
Size 209.7 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
02d1ddcc7ce70d6d0091b8573a824ee766ead74ba7d2b4032cd9be590269146f
BLAKE2b-256 checksum
How to use checksums
140c311e99fd3e1acf5303fd4c9c1613f13bdf577e8be6da873c244f8ca2c487
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.6 MB
Tags CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
bb778fc7af792de3eee4dc07334f3ad16faa98ba9ddcfafee6dc6f9f97ce163f
BLAKE2b-256 checksum
How to use checksums
97cbd6f5e39ab553c5890e1045a98cc4228c68b67af8eb1f149d99a5b8e6aa28
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl

Download URL unifyvcf-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl
Size 244.6 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
6db696a35fca722520a240bef026946b9752f12b2a6ecb838dee3c3ff10df404
BLAKE2b-256 checksum
How to use checksums
5f7029976c5c779e65184fc84eac0f75664158b7c0f0b40313a3ce651f281cca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp311-cp311-win_amd64.whl

Download URL unifyvcf-0.2.0-cp311-cp311-win_amd64.whl
Size 215.9 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
ad585562ff16c3a5ad6b3356c8f8f4d255f85b7c01d5d131f437d9b73b6c97a9
BLAKE2b-256 checksum
How to use checksums
b51259f507cca5725c8d811a6006b7291d03486ab91ddcda792f3d925017a4d7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
50d3b6440bf3d59c98ab6f9f32e33dc5ee16d4caac3737f32571ec6a248a68a1
BLAKE2b-256 checksum
How to use checksums
0ced251b0d510d247abe1dacbb60ee71ce4008aa3bce36deef1c570724f6ac9c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl
Size 241.4 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
95f28fbca672ccae07dda65ef01a50bc53e51c6112965c211eaed30d2de7ff37
BLAKE2b-256 checksum
How to use checksums
4c9f8b38dedde7b675d94b60fd24880c2cf046f762dadf3d39de87ac86bc2828
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp310-cp310-win_amd64.whl

Download URL unifyvcf-0.2.0-cp310-cp310-win_amd64.whl
Size 216.9 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
24fe05142734f292d88c14b56b761f28b57e58ea02ad9f796cbe76f1803cc6f0
BLAKE2b-256 checksum
How to use checksums
61946e2b4d05b56749f76b66f1ac422f5211d1d807313eb007e77b40a31cde7e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
8abc00b4e807c2f17da9427f94711032540d13510b76b91047d2f8c9eccd8f8c
BLAKE2b-256 checksum
How to use checksums
b7f8b33f3ab268dbc47d55c535b48519bd79e9a5e664797e15e8f9d962448c8d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl
Size 245.3 kB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
eeef082ea54abb5786f7cd26581b6bdc055640a99f1ea27cb7597ee5d21cabb9
BLAKE2b-256 checksum
How to use checksums
a3698d074c0c7ffbb5373be768aa28e3b966a7a22bba74dcd2629b609635db2a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp39-cp39-win_amd64.whl

Download URL unifyvcf-0.2.0-cp39-cp39-win_amd64.whl
Size 217.7 kB
Tags CPython 3.9 Windows x86-64
SHA-256 checksum
How to use checksums
a31f30ee299692c97118d689756fcc6a2798ad98f4a19385422578d3b025dad4
BLAKE2b-256 checksum
How to use checksums
5e67c2297691b6999dd36a1fceabd4b09bbe7ec45cf8e7e195005b0d401b59d1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL unifyvcf-0.2.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 1.5 MB
Tags CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
1ab69c3fa3b752857d1a13719aa17369bc427326af2945dbe3e27addec0290cc
BLAKE2b-256 checksum
How to use checksums
39a940636cc2be3392cecad405898d4d6e0da7e7284873e4df9508ff0391fdc3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Release files / unifyvcf-0.2.0-cp39-cp39-macosx_10_9_x86_64.whl

Download URL unifyvcf-0.2.0-cp39-cp39-macosx_10_9_x86_64.whl
Size 246.6 kB
Tags CPython 3.9 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
96dab778e07379e7d354ea7dc64658e73f5c8d50a918f7efdd508069deeae252
BLAKE2b-256 checksum
How to use checksums
8ecce8b3ccdd2339fc0f4874d394521d80e5be1c93474cbae7acf053250e1bba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.16

Security for UnifyVcf 0.2.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page