<commit_before>[![Package quality](http://packagequality.com/shield/package-quality.svg)](http://packagequality.com/#?package=package-quality)
[![Build Status](https://secure.travis-ci.org/alexfernandez/package-quality.svg)](http://travis-ci.org/alexfernandez/package-quality)

[![Package quality](http://packagequality.com/badge/package-quality.png)](http://packagequality.com/#?package=package-quality)

# package-quality

Measurements of quality for packages, [initially for npm](http://npm.packagequality.com/).

## Add Your Badge

To show the quality of your npm package, just add one of these images to your GitHub README:

```
[![Package quality](http://packagequality.com/shield/yourpackage.svg)](http://packagequality.com/#?package=yourpackage)
[![Package quality](http://packagequality.com/badge/yourpackage.png)](http://packagequality.com/#?package=yourpackage)
```

Or, in HTML markup:

```
<a href="http://packagequality.com/#?package=yourpackage"><img src="http://packagequality.com/badge/yourpackage.png"/></a>
<a href="http://packagequality.com/#?package=yourpackage"><img src="http://packagequality.com/shield/yourpackage.svg"/></a>
```

replacing `yourpackage` with (surprise!) the name of your package.
You can choose between badge or mini-badge (the latter is courtesy of shields.io).

## Measuring Quality

Any objective measurements of quality are going to be flawed one way or another.
`package-quality` only attempts to give some indications about quality,
not be an absolute rating on which to bet your farm.
If you don't agree with our ratings, please [help us improve them](https://github.com/alexfernandez/package-quality/pulls)!
<commit_msg>Link to shields.io.<commit_after>[![Package quality](http://packagequality.com/shield/package-quality.svg)](http://packagequality.com/#?package=package-quality)
[![Build Status](https://secure.travis-ci.org/alexfernandez/package-quality.svg)](http://travis-ci.org/alexfernandez/package-quality)

[![Package quality](http://packagequality.com/badge/package-quality.png)](http://packagequality.com/#?package=package-quality)

# package-quality

Measurements of quality for packages, [initially for npm](http://npm.packagequality.com/).

## Add Your Badge

To show the quality of your npm package, just add one of these images to your GitHub README:

```
[![Package quality](http://packagequality.com/shield/yourpackage.svg)](http://packagequality.com/#?package=yourpackage)
[![Package quality](http://packagequality.com/badge/yourpackage.png)](http://packagequality.com/#?package=yourpackage)
```

Or, in HTML markup:

```
<a href="http://packagequality.com/#?package=yourpackage"><img src="http://packagequality.com/badge/yourpackage.png"/></a>
<a href="http://packagequality.com/#?package=yourpackage"><img src="http://packagequality.com/shield/yourpackage.svg"/></a>
```

replacing `yourpackage` with (surprise!) the name of your package.
You can choose between badge or mini-badge; the latter is courtesy of [shields.io](http://shields.io).

## Measuring Quality

Any objective measurements of quality are going to be flawed one way or another.
`package-quality` only attempts to give some indications about quality,
not be an absolute rating on which to bet your farm.
If you don't agree with our ratings, please [help us improve them](https://github.com/alexfernandez/package-quality/pulls)!

{'fraction_non_alphanumeric': 0.15359477124183007, 'fraction_numerical': 0.0, 'mean_word_length': 5.815789473684211, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 15, 'https://': 4, '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': '582193', 'n_tokens_mistral': 1028, 'n_tokens_neox': 967, 'n_words': 242}