Vcfvalidator

Latest version: v1.0.3

Safety actively analyzes 693883 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

0.4

In addition to the removal of duplicate variants introduced in the previous release, errors in the INFO and samples columns can be fixed now by removing the faulty field from the column. For instance, if an INFO value looks like `AN=123;AF=not_a_frequency;DP=345`, the fix would transform it into `AN=123;DP=345`.

Other improvements included in this version are:
- Support for genomic ploidy different from 2
- Ensuring all the variants that don't require fixing are written after running the vcf-debugulator
- Simplified build process using a Docker image (recommended for developers only)

You can download the executables using the links below.

0.3

This release brings many exciting new features! VCF v4.3 is now supported and has been tested against more than 150 VCF files, so you can be sure it will catch a lot of pesky errors.

To make error solving a bit easier, vcf-validator now contains 2 different tools:
- The validator, which can write reports to plain text and now also to a portable database (SQLite). Then the user doesn't need to fix every error by hand, because this database can be later processed by an automated tool such as...
- The "debugulator", which reads the validator reports and automatically corrects as many errors as possible. This version can remove duplicated variants, and we will add [more fixes in the future](https://github.com/EBIvariation/vcf-validator/issues/39). In this release, the debugulator support is experimental and has some important bugs that were fixed in newer versions.

0.2.2

Support for multiple compilers has been improved and it is automatically checked when committing changes to the repository. The list of fully supported compilers is:
- Clang 3.5 to 3.7
- GCC 4.8 to 5.0

0.2.1

Static linking is now supported during the build process, benefiting those who can't install the dependencies in the machine that will run the validator.

If that is your case, please run the build in a system where you have root permissions, adding the `-DBUILD_STATIC=1` option to the `cmake` command.

0.2

This version introduces support for different validation levels: check only errors, errors and warnings, or stop after the first error is found.

The previous version didn't handle properly all the corner cases in meta-data descriptions. Empty descriptions and those containing escaped quotes are now considered valid.

Warnings are now raised when:
- A comma is found in the ID column
- The POS column value is zero

Please check [the milestone information](https://github.com/cyenyxe/vcf-validator/issues?q=milestone:0.2) for a detailed description of resolved issues.

0.1

First working version of the validator, supporting VCF 4.1 and 4.2 via a formal grammar implemented using the Ragel State Machine Compiler (http://www.colm.net/open-source/ragel/).

It has been tested against all the files submitted to the European Variation Archive (www.ebi.ac.uk/eva) up to this date. More stand-alone tests are being implemented and will be included in future releases.

Page 3 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.