<commit_before>conda-verify
============
[![Travis branch](https://img.shields.io/travis/conda/conda-verify/master.svg?style=flat-square)](https://travis-ci.org/conda/conda-verify) [![Codecov branch](https://img.shields.io/codecov/c/github/conda/conda-verify/master.svg)](https://codecov.io/gh/conda/conda-verify)

conda-verify is a tool for (passively) verifying conda recipes and
conda packages. The purpose of this verification process is to ensure that
recipes don't contain obvious bugs, and that the conda packages we distribute
to millions of users meet our high quality standards.

Features
--------

Another aspect of `conda-verify` is the ability to verify conda packages.
These are the most important checks `conda-verify` performs on conda
packages, and more importantly we explain why these checks are necessary
or useful.

  * Ensure the content of `info/files` corresponds to the actual archived
    files in the tarball (except the ones in `info/`, obviously).  This
    is important, because the files listed in `info/files` determine which
    files are linked into the conda environment.  Any mismatch here would
    indicate either (i) the tarball contains files which are not getting<commit_msg>Use same badge style on codecov badge as travis badge<commit_after>conda-verify
============
[![Travis branch](https://img.shields.io/travis/conda/conda-verify/master.svg?style=flat-square)](https://travis-ci.org/conda/conda-verify)
[![Codecov branch](https://img.shields.io/codecov/c/github/conda/conda-verify/master.svg?style=flat-square)](https://codecov.io/gh/conda/conda-verify)

conda-verify is a tool for (passively) verifying conda recipes and
conda packages. The purpose of this verification process is to ensure that
recipes don't contain obvious bugs, and that the conda packages we distribute
to millions of users meet our high quality standards.

Features
--------

Another aspect of `conda-verify` is the ability to verify conda packages.
These are the most important checks `conda-verify` performs on conda
packages, and more importantly we explain why these checks are necessary
or useful.

  * Ensure the content of `info/files` corresponds to the actual archived
    files in the tarball (except the ones in `info/`, obviously).  This
    is important, because the files listed in `info/files` determine which
    files are linked into the conda environment.  Any mismatch here would
    indicate either (i) the tarball contains files which are not getting
{'fraction_non_alphanumeric': 0.09678714859437751, 'fraction_numerical': 0.0, 'mean_word_length': 4.523281596452328, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '586067', 'n_tokens_mistral': 694, 'n_tokens_neox': 682, 'n_words': 280}