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/*.pyitype stubs carrying every public signature and its description, generated from the source bytools/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 goodfrom UnifyVcf.cli import dragen_from_cliis reported asE0611: No name 'dragen_from_cli' in module 'UnifyVcf.cli'.__init__.pystays interpreted, so pylint reads the names straight out of it andfrom UnifyVcf import dragen_from_clianalyses 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=REPand 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
bgzipwas logged and execution continued, leaving an unsorted, uncompressed.vcfwhere the caller expected.vcf.gz. Failures now raise. - Its temp directory was
vcf-tempin 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 afinally.
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.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 11.8 MB
Release files / unifyvcf-0.2.2-cp314-cp314-win_amd64.whl
| Download URL | unifyvcf-0.2.2-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 211.4 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c705f7feb7fe462681d749052180d71f327ee4414d720875908f4fc1e8d5e7fe
|
|
BLAKE2b-256 checksum How to use checksums |
2f80a1f9cbac1d59f4b6da8c9462d4d922147c25389a2812bd797f42147a2d3b
|
| 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.2-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | unifyvcf-0.2.2-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.5 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
4ae68e81bc4b710d8e202b23e37e5f3310410430b40e113637e3b03b111dcbb8
|
|
BLAKE2b-256 checksum How to use checksums |
2e9d2e0ca2a40050b899dee9a6fee858bec327466faec4b2675ddc844bb7a909
|
| 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.2-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | unifyvcf-0.2.2-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 243.8 kB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
7aa697f3627de457454f85b1c3fc92535e49a12150b9684edeb204f8fd5c8c1d
|
|
BLAKE2b-256 checksum How to use checksums |
c4a851f3d8e62b24ed2b98167589d9c457cd6f7c2133ba6e38b4e120294672dc
|
| 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.2-cp313-cp313-win_amd64.whl
| Download URL | unifyvcf-0.2.2-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 208.6 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
140bfaa48a49bf4eb78800f3b1b8fa7e2e78dba9a43eb4ec1d895d29b73bcbfa
|
|
BLAKE2b-256 checksum How to use checksums |
e158518f60d84802a2cbb4ca3610c2c78b36b396380021bd53471cf58a9d699a
|
| 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.2-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | unifyvcf-0.2.2-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 |
60c6d6dbcf1f8acc3e5a7bb5ac7e906dcdeb3e1212b96e702cdf85f0d9606840
|
|
BLAKE2b-256 checksum How to use checksums |
70dc06b75c40dab4dff20bf890c37079cbf44e16ee79704192a276e41483a79c
|
| 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.2-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | unifyvcf-0.2.2-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 243.8 kB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
4f6361af114ea9accab00413cb8a409d2979a49776514b155b1d7d3ac93a0e49
|
|
BLAKE2b-256 checksum How to use checksums |
6f2d329991a73400ef3b4aa38c7c4cae276f5cf75d5c399bc953d5bbfe019537
|
| 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.2-cp312-cp312-win_amd64.whl
| Download URL | unifyvcf-0.2.2-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 210.0 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
dd069b98507e9f01f4cc7222849c3e0f27395fbf705351f21b287c85a48136bd
|
|
BLAKE2b-256 checksum How to use checksums |
778c548c031e494e260babe5ba5787ac88f5dc6a302b325775939ac2f140a70a
|
| 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.2-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | unifyvcf-0.2.2-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 |
d4a0c6338d588517dfca0e8cea64236eb767885963990b54235a9dfcbb822a1d
|
|
BLAKE2b-256 checksum How to use checksums |
14ae352d77cf1cbb9858a5c85c73192f6b28abe24a02a164c3094df2ea1f1616
|
| 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.2-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | unifyvcf-0.2.2-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 244.9 kB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
726362719a8db1bdd7d615057e7616aae9164e59de98812cc0c9e91b4b1e2c97
|
|
BLAKE2b-256 checksum How to use checksums |
ccdcd73d81a5349b7f698209a552fcf08d5f3b4c3bcba18145b6f7ba5ae89f22
|
| 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.2-cp311-cp311-win_amd64.whl
| Download URL | unifyvcf-0.2.2-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 216.2 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
087a22b4b049a10bac76c35293039c6903a37a8d52462a81287463c7683b5181
|
|
BLAKE2b-256 checksum How to use checksums |
4c408a31f9291f4dfc50d5370d186d8bb77b20ff8f67a5bf0f1b694acf1fdf33
|
| 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.2-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | unifyvcf-0.2.2-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 |
7f4ac9b802e5b40a32c5e5f1cb6c71c72ba197cafde4fab715dec54c239c6d47
|
|
BLAKE2b-256 checksum How to use checksums |
8d69913b2c19871340bbfb0678ff80f2d2216d61dd595d247d5cfbaa5b31342e
|
| 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.2-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | unifyvcf-0.2.2-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 241.6 kB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
6837a14b24beee80626146b6669b057f5b117669c4796fd4c0be3205fcf3cbdf
|
|
BLAKE2b-256 checksum How to use checksums |
0b642e9fde138f0034fc7654e5eb517b64b62abc6f916ffc2bb7d9b15117da02
|
| 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.2-cp310-cp310-win_amd64.whl
| Download URL | unifyvcf-0.2.2-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 217.2 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
afe6422fb503fc7e91a4a33643e9c820ba6c5906d64ddc683cb55b4ade3bb48c
|
|
BLAKE2b-256 checksum How to use checksums |
abb69a1c97376a7780457badf5f14a8713948f0052196f4b4aa1f7def9a64938
|
| 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.2-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | unifyvcf-0.2.2-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 |
2957ef3b3c16a65b6bdf2bb474be621f5f1f2c54479167f74511305d9de0995f
|
|
BLAKE2b-256 checksum How to use checksums |
095b2c06b9392ce7b7c8d59519b59520344d2c3d4f598d74526951d1cf21511c
|
| 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.2-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | unifyvcf-0.2.2-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 245.6 kB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
dd40f1e571c3fb022a4431f68754e262eb258a8854e81042d43b79cde4a1f769
|
|
BLAKE2b-256 checksum How to use checksums |
95e97cce526d1ece35357eab39e868cacc812ce85c010f426646f672f8e73048
|
| 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.2-cp39-cp39-win_amd64.whl
| Download URL | unifyvcf-0.2.2-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 217.9 kB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
67dfe19fa4570261e90950b56d426d0cca4d7f27e1d7a8be7159feec33ba180c
|
|
BLAKE2b-256 checksum How to use checksums |
388b22261d0d9f81d53ccc6d5292d8301c0e2ae671bbd71291c7a3813f39ae9e
|
| 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.2-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | unifyvcf-0.2.2-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 |
629edc7ca441cf84bcc49370171eda0c8562383c14dfe692195bb06ea55e8147
|
|
BLAKE2b-256 checksum How to use checksums |
8c0f7576db4dd290320968b66e7c5ed3dc897b04536c090416c8e25b3564a975
|
| 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.2-cp39-cp39-macosx_10_9_x86_64.whl
| Download URL | unifyvcf-0.2.2-cp39-cp39-macosx_10_9_x86_64.whl |
|---|---|
| Size | 246.9 kB |
| Tags | CPython 3.9 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
31d0b9bb4fde014f2b09a385ce5b1517fd26af2fb3d6f6b8e014a8a9b1128c53
|
|
BLAKE2b-256 checksum How to use checksums |
8579e5eeed4b7d2ee022286eff9c4f5a90678be51c9e310b9a49cb98f68e5bee
|
| 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.2
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.