jsonid 0.12.3
jsonid a json identification tool
Requires Python: >=3.11
Keywords: json, digipres, file-formats

# JSONID

<!-- markdownlint-disable -->
<img
    src="https://github.com/ffdev-info/jsonid/blob/main/static/images/JSON_logo-crockford.png?raw=true"
    alt="JSON ID logo based on JSON Logo by Douglas Crockford"
    width="200px" />

<!-- markdownlint-enable -->

[**JSONID**][json-1]entification tool and ruleset. JSONID can be downloaded
from pypi.org.

<!-- markdownlint-disable-->

[![PyPI - Version](https://img.shields.io/pypi/v/jsonid?style=plastic&color=purple)][pypi-json-id-1]&nbsp;[![Static Badge][shield-io]][coptr-1]

[json-1]: https://www.json.org/json-en.html
[pypi-json-id-1]: https://pypi.org/project/jsonid/
[shield-io]: https://img.shields.io/badge/COPTR-JSONID-purple
[coptr-1]: https://coptr.digipres.org/JSONID

## Contents

<!-- via: https://luciopaiva.com/markdown-toc/ -->

- [Before you begin](#before-you-begin)
  - [MacOS](#macos)
  - [Windows](#windows)
  - [Linux](#linux)
- [Introduction to JSONID](#introduction-to-jsonid)
- [Why?](#why)
  - [Encodings](#encodings)
  - [Enxodings explained](#enxodings-explained)
- [What does JSONID get you?](#what-does-jsonid-get-you)
- [Ruleset](#ruleset)
  - [Backed by tests](#backed-by-tests)
- [Sample files](#sample-files)
  - [Integration files](#integration-files)
  - [Fundamental examples](#fundamental-examples)
- [Registry](#registry)
  - [Registry examples](#registry-examples)
  - [Local rules](#local-rules)
- [PRONOM](#pronom)
- [Output format](#output-format)
  - [Agent out](#agent-out)
- [Lookup](#lookup)
  - [Core formats](#core-formats)
  - [Doctype formats](#doctype-formats)
- [JSONL](#jsonl)
  - [Handling JSONL](#handling-jsonl)
- [Analysis](#analysis)
  - [Example analysis](#example-analysis)
  - [JSONL technical metadata](#jsonl-technical-metadata)
- [Utils](#utils)
  - [json2json](#json2json)
- [Docs](#docs)
- [Developer install](#developer-install)
  - [pip](#pip)
  - [tox](#tox)
  - [pre-commit](#pre-commit)
- [Packaging](#packaging)
  - [pyproject.toml](#pyprojecttoml)
  - [Versioning](#versioning)
  - [Local packaging](#local-packaging)
  - [Publishing](#publishing)

## Before you begin

JSONID should run out of the box but it can be difficult to get everything
running correctly across all platforms without some effort. Additional
install instructions are listed below before you dig into everything in
more detail.

### MacOS

* MacOS users may need to run `brew install libmagic` to install libmagic
dependencies associated with compressed JSONL.

### Windows

* There are no known exceptions for Windows at present, that being said
an absence of libmagic on Windows means compressed JSONL cannot be
identified just yet.

### Linux

* There are no known exceptions for Linux users.

## Introduction to JSONID

JSONID is designed to identify data we recognize as JSON, YAML, TOML,
and JSONL (currently a non-exhaustive list that can easily be extended).

JSON, YAML, TOML, and JSONL, are all serialization formats; that is, when a
computer program wants to persist data from memory to disk, it serializes
the data into a serialization format. When the same program wants to read
the data back into memory, it deserializes the structures from disk. These
formats are also called "serde," a combination the words
ser(ialize) and de(serialize).

JSONID borrows from the Python approach to ask forgiveness rather than
permission (EAFP) to attempt to open every object it scans and see if it
parses as JSON. If it doesn't, we move along. If it does, we then have an
opportunity to identify the characteristics of the JSON we have opened.

Python being high-level also provides an easier path to processing files
and parsing JSON quickly with very little other knowledge required
of the underlying data structure.

## Why?

Consider these equivalent forms:

```json
{
    "key 1": "value",
    "key 2": "value"
}
```

```json
{
    "key 2": "value",
    "key 1": "value"
}
```

PRONOM signatures are not expressive enough for complicated JSON objects.

If I want DROID to find `key 1` I have to use a wildcard, so I would write
something like:

```text
BOF: "7B*226B6579203122"
EOF: "7D"
```

But if I then want to match on `key 2` as well as `key 1` things start getting
complicated as they aren't guaranteed by the JSON specification to be in the
same "position" (if we think about order visually). When other keys are used in
the object they aren't even guaranteed to be next to one another.

This particular example is a 'map' object whose most important property
is consistent retrieval of information through its "keys". Further
complexity can be added when we are dealing with maps embedded in a "list" or
"array", or simply just maps of arbitrary depth.

JSONID tries to compensate for JSON's complexities by using the format's
own strengths to parse binary data as JSON and then if is successful,
use a JSON-inspired grammar to describe keys and key-value pairs as "markers"
that can potentially identify the JSON objects that we are looking at.
Certainly narrow down the potential instances of JSON objects that we might
be looking at.

### Encodings

A better reason might appear if we look at encodings. Look at the following
hexdumps:

#### UTF-16LE

```text
$ hexdump -C UTF-16LE-map.json
00000000  7b 00 22 00 61 00 22 00  3a 00 20 00 22 00 62 00  |{.".a.".:. .".b.|
00000010  22 00 7d 00 0a 00                                 |".}...|
00000016
```

#### UTF-16BE

```text
$ hexdump -C UTF-16BE-map.json
00000000  00 7b 00 22 00 61 00 22  00 3a 00 20 00 22 00 62  |.{.".a.".:. .".b|
00000010  00 22 00 7d 00 0a                                 |.".}..|
00000016
```

#### UTF-32BE

```text
$ hexdump -C UTF-32BE-map.json
00000000  00 00 00 7b 00 00 00 22  00 00 00 61 00 00 00 22  |...{..."...a..."|
00000010  00 00 00 3a 00 00 00 20  00 00 00 22 00 00 00 62  |...:... ..."...b|
00000020  00 00 00 22 00 00 00 7d  00 00 00 0a              |..."...}....|
0000002c
```

#### UTF-32LE

```text
$ hexdump -C UTF-32LE-map.json
00000000  7b 00 00 00 22 00 00 00  61 00 00 00 22 00 00 00  |{..."...a..."...|
00000010  3a 00 00 00 20 00 00 00  22 00 00 00 62 00 00 00  |:... ..."...b...|
00000020  22 00 00 00 7d 00 00 00  0a 00 00 00              |"...}.......|
0000002c
```

#### UTF-8

```text
$ hexdump -C UTF-8-map.json
00000000  7b 22 61 22 3a 20 22 62  22 7d 0a                 |{"a": "b"}.|
0000000b
```

### Enxodings explained

Each of the hexdumps shown are the equivalent of different files on disk, but
each of those files encodes exactly the same information. The difference is
how the information was encoded using a character set that could *potentially*
store more information, but ultimately does not.

It is entirely possible to deserialize these files to exactly the same
structure in memory, at which point JSONID can begin to assert equivalence
and output the underlying document type as well as other information.

If we want to understand the complexity required to write a PRONOM signature
to account for different encodings, look at how the `00` bytes are
placed between examples. We have to be able to encode the bytes we know about,
as well as the bytes that are output as part of the encoding. If we treat
the UTF-8 version of the file above as the primary object, but say, we want
to find all versions if they exist, we need to write four other signatures
(at least, before we even talk about whitespace). This is difficult for
a human.

I hope with JSONID we will soon be able to use the JSONID declarative
language to automatically output PRONOM-compatible signatures.

This means, in the example above, we can encode one ruleset in JSONID which
will work for all variants given to JSONID. We can then output five or more
PRONOM-compatible signatures that can be given to the PRONOM registry
to improve their capabilities in the future. That's five signatures for
the price of one and it gives JSONID a unique way of contributing back to
a core resource in digital preservation.

## What does JSONID get you?

To begin, JSONID should identify JSON files on your system as JSON.
That's already a pretty good position to be in.

The ruleset should then allow you to identify a decent number of JSON objects,
especially those that have a well-defined structure. Examples we have in the
[registry data][registry-htm-1] include things like ActivityPub streams,
RO-CRATE metadata, IIIF API data and so on.

If the ruleset works for JSON we might be able to apply it to other formats
that can represent equivalent data structures in the future
such as [YAML][yaml-spec], and [TOML][toml-spec].

[yaml-spec]: https://yaml.org/
[toml-spec]: https://toml.io/en/

## Ruleset

JSONID currently defines a small set of rules that help us to identify JSON
documents.

The rules are described in their own data-structures. The structures are
processed as a list (they need not necessarily be in order) and each must
match for a given set of ruls to determine what kind of JSON document we might
be looking at.

JSONID can identify the existence of information but you can also use
wildcards and provide some negation as required, e.g. to remove
false-positives between similar JSON entities.

| rule       | meaning                                               |
|------------|-------------------------------------------------------|
| INDEX      | index (from which to read when structure is an array) |
| GOTO       | goto key (read key at given key)                      |
| KEY        | key to read                                           |
| CONTAINS   | value contains string                                 |
| STARTSWITH | value startswith string                               |
| ENDSWITH   | value endswith string                                 |
| IS         | value matches exactly                                 |
| REGEX      | value matches a regex pattern                         |
| EXISTS     | key exists                                            |
| NOEXIST    | key doesn't exists                                    |
| ISTYPE     | key is a specific type (string, number, dict, array)  |

Stored in a list within a `RegistryEntry` object, they are then processed
in order.

For example:

```json
    [
        { "KEY": "name", "IS": "value" },
        { "KEY": "schema", "CONTAINS": "/schema/version/1.1/" },
        { "KEY": "data", "IS": { "more": "data" } },
    ]
```

All rules need to match for a positive ID.

> **NB.**: JSONID is a
work-in-progress and requires community input to help determine the grammar
in its fullness and so there is a lot of opportunity to add/remove to these
methods as its development continues. Additionally, help formalizing the
grammar/ruleset would be greatly appreciated 🙏.

### Backed by tests

The ruleset has been developed using test-driven-development practices (TDD)
and the current set of tests can be reviewed in the repository's
[test folder][testing-1]. More tests should be added, in general, and over
time.

Run `just coverage` to see JSONID's current level of test coverage.

[testing-1]: https://github.com/ffdev-info/jsonid/tree/main/tests

## Sample files

### Integration files

Files used in the development of JSONID are available in their
[own repository][integration-1].

[integration-1]: https://github.com/ffdev-info/jsonid-integration-files

### Fundamental examples

There is a small [samples directory][samples-1] included with this
epository demonstrating some fundamental differences in encoding and
JSON types.

[samples-1]: samples/

## Registry

A temporary "registry" module is used to store JSON markers.
The registry is a work in progress and must be exported and
rewritten somewhere more centralized (and easier to manage) if JSONID can
prove useful to the communities that might use it (*see notes on PRONOM below*).

The registry web-page is here:

* [JSONID registry][registry-htm-1].

[registry-htm-1]: https://ffdev-info.github.io/jsonid/registry/

The registry's source is here:

* [Registry](https://github.com/ffdev-info/jsonid/blob/main/src/jsonid/registry_data.py).

### Registry examples

#### Identifying JSON-LD Generic

```python
    RegistryEntry(
        identifier="id0009",
        name=[{"@en": "JSON-LD (generic)"}],
        markers=[
            {"KEY": "@context", "EXISTS": None},
            {"KEY": "id", "EXISTS": None},
        ],
    ),
```

> **Pseudo code**:
Test for the existence of keys: `@context` and `id` in the primary JSON object.

#### Identifying Tika Recursive Metadata

```python
    RegistryEntry(
        identifier="id0024",
        name=[{"@en": "tika recursive metadata"}],
        markers=[
            {"INDEX": 0, "KEY": "Content-Length", "EXISTS": None},
            {"INDEX": 0, "KEY": "Content-Type", "EXISTS": None},
            {"INDEX": 0, "KEY": "X-TIKA:Parsed-By", "EXISTS": None},
            {"INDEX": 0, "KEY": "X-TIKA:parse_time_millis", "EXISTS": None},
        ],
```

> **Pseudo code**:
Test for the existence of keys: `Content-Length`, `Content-Type`,
`X-TIKA:Parsed-By` and `X-TIKA:parse_time_millis` in the `zeroth` (first)
JSON object where the primary document is a list of JSON objects.

#### Identifying SOPS encrypted secrets file

```python
    RegistryEntry(
        identifier="id0012",
        name=[{"@en": "sops encrypted secrets file"}],
        markers=[
            {"KEY": "sops", "EXISTS": None},
            {"GOTO": "sops", "KEY": "kms", "EXISTS": None},
            {"GOTO": "sops", "KEY": "pgp", "EXISTS": None},
        ],
    ),
```

> **Pseudo code**:
Test for the existence of keys `sops` in the primary JSON object.
>
> Goto the `sops` key and test for the existence of keys: `kms` and `pgp`
within the `sops` object/value.

### Local rules

The plan is to allow local rules to be run alongside the global ruleset. I
expect this will be a bit further down the line when the ruleset and
metaddata is more stabilised.

## PRONOM

Ideally JSON can generate evidence enough to warrant the creration of
PRONOM IDs that can then be referenced in the JSONID output.

Evantually, PRONOM or a PRONOM-like tool might host an authoritative version
of the JSONID registry.

### JSONID for PRONOM Signature Development

JSONID provides a high-level language for output of PRONOM compatible
signatures. The feature set is still in its BETA phase but JSONID provides
two distinct capabilities:

#### 1. Registry output

JSONID's registry can be output using the `--pronom` flag. A signature file
will be created under `jsonid_pronom.xml` which can be imported into DROID
for identification of document types registered with JSONID.

JSONID's registry is output alongisde a handful of baseline JSON signatures
designed to capture "plain"-JSON that is not yet encoded in the registry.

#### 2. Signature development

A standalone `json2pronom` utility is provided for creation of potentially
robust DROID compatible signatures.

As a high-level language, signatures can be defined in easy to understand
syntax and then output consistently via the `json2pronom` utility. Signatures
include sensible defaults for whitespace and other aspects that are
difficult for signature developers to consistently anticipate when writing
JSON based signatures. One particular benefit of using `json2pronom` is that
it can automatically output JSON signatures using different
character encodings which use a lot of excess characters difficult for
humans to format correctly into a DROID compatible format.

Given a [sample pattern file](./pronom_example/patterns_example.json) a DROID
compatible snippet can be output as follows (UTF-8 shown for brevity):

<!--markdownlint-disable-->

```xml
<?xml version="1.0" ?>
<FFSignatureFile xmlns="http://www.nationalarchives.gov.uk/pronom/SignatureFile" Version="1" DateCreated="2026-01-04T16:14:16Z">
  <InternalSignatureCollection>
    <InternalSignature ID="1" Specificity="Specific">
      <ByteSequence Reference="BOF" Sequence="{0-4095}7B" MinOffset="0" MaxOffset="4095"/>
      <ByteSequence Reference="VAR" Sequence="226B65793122{0-16}3A" MinOffset="" MaxOffset=""/>
      <ByteSequence Reference="VAR" Sequence="226B65793222{0-16}3A" MinOffset="" MaxOffset=""/>
      <ByteSequence Reference="EOF" Sequence="7D{0-4095}" MinOffset="0" MaxOffset="4095"/>
    </InternalSignature>
  </InternalSignatureCollection>
  <FileFormatCollection>
    <FileFormat ID="1" Name="JSONID2PRONOM Conversion (UTF-8)" PUID="jsonid2pronom/1" Version="" MIMEType="application/json" FormatType="structured text">
      <InternalSignatureID>1</InternalSignatureID>
      <Extension>json</Extension>
    </FileFormat>
</FFSignatureFile>
```

<!--markdownlint-enable-->

Feedback on this utility is welcome. Hopefully we can build on this
approach for other structured formats such as XML.

## Output format

Previously JSONID output YAML containing all result object metadata. It has
since coalesced on a MIME based output approximating that of `$file --mime`.
Exceptions include the ability to output multiple IDs separated by `|` and
a count describing how many identifiers were returned.

> NB. it is still a goal of JSONID to avoid multiple IDs but serde formats
are as flexible as they need to be and will not always behave well.

An example output looks as follows.

<!--markdownlint-disable-->

```text
samples/encoding/UTF-16LE-map.json	[1]	application/json; charset=UTF-16; doctype="JavaScript Object Notation (JSON)"; ref=jrid:JSON
samples/encoding/UTF-32LE-list.json	[1]	application/json; charset=UTF-32; doctype="JavaScript Object Notation (JSON)"; ref=jrid:JSON
```

```text
integration_files/json/mame/mame-hiscore-plugin.json    [1]	application/json; charset=UTF-8; doctype="MAME Plugin (JSON)"; ref=jrid:0073
integration_files/jsonl/asciicast/asciicast-v2.jsonl    [1]	application/jsonl; charset=UTF-8; doctype="asciicast (asciinema.org) v2"; ref=jrid:0079
```

You can see a demonstration of multiple identification output in the
integration tests.

```text
test_file.json  [2] application/json; charset=UTF-8; doctype="MULTI_ID_1"; ref=jrid:0001 | application/json; charset=UTF-8; doctype="MULTI_ID_2"; ref=jrid:0002
```

### Agent out

The `--agentout` arg makes JSONID output a full JSON snippet complete with
version information for integration into workflows in digital preservation
systems. Example output:

```json
{
  "path": "samples/encoding/UTF-16-map_whitespace.json",
  "results": [
    "application/json; charset=UTF-16; doctype=\"JavaScript Object Notation (JSON)\"; ref=jrid:JSON"
  ],
  "count": 1,
  "agent": "jsonid/0.0.0 (ffdev-info)"
}
```

<!--markdownlint-enable-->

## Lookup

Registry metadata is no longer output in results. As such, a `lookup` function
is provided to return that information. See for example:

### Core formats

```text
python jsonid.py core JSON
```

```yaml
name:
- '@en': JavaScript Object Notation (JSON)
mime:
- application/json
documentation:
- archive_team: http://fileformats.archiveteam.org/wiki/JSON
identifiers:
- rfc: https://datatracker.ietf.org/doc/html/rfc8259
- pronom: http://www.nationalarchives.gov.uk/PRONOM/fmt/817
- loc: https://www.loc.gov/preservation/digital/formats/fdd/fdd000381.shtml
- wikidata: https://www.wikidata.org/entity/Q2063
```

### Doctype formats

```text
python jsonid.py lookup jrid:0055
```

```yaml
name:
- '@en': Lottie vector graphics
mime: []
description:
- '@en': a animated file format using JSON also known as Bodymovin JSON
documentation:
- archive_team: http://fileformats.archiveteam.org/wiki/Lottie
identifiers:
- rfc: ''
- pronom: ''
- loc: ''
- wikidata: http://www.wikidata.org/entity/Q98855048
```

## JSONL

[JSONL][jsonl-1] aka JSON Lines is a format that requires some special
handling in the code, first to detect whether content is in an
"archive format" (archive in computer science terms) or aggregate (in
PRONOM terms); and then process the content reliably.

### Handling JSONL

JSONL will be treated as follows:

1. if a file is identified as JSONL a JSONL identification will always be
returned. This will always be reliable.
1. the first line of the JSONL file is treated as the authoritative object,
that is, all other lines are expected to conform to the same schema. If
the object can be matched against a ruleset the ID will be returned. If the
object cannoot be matched against a ruleset then an identification of
JSONL will be returned. All other lines are ignored.

[jsonl-1]: https://jsonlines.org/

## Analysis

JSONID provides an analysis mechanism to help developers of identifiers. It
might also help users talk about interesting properties about the objects
being analysed, and provide consistent fingerprinting for data that has
different byte-alignment but is otherwise identical.

> **NB.**: Comments on existing statistics or ideas for new ones are
appreciated.

### Example analysis

```json
{
  "content_length": 329,
  "number_of_lines": 32,
  "line_warning": false,
  "top_level_keys_count": 4,
  "top_level_keys": [
    "key1",
    "key2",
    "key3",
    "key4"
  ],
  "top_level_types": [
    "list",
    "map",
    "list",
    "list"
  ],
  "depth": 8,
  "heterogeneous_list_types": true,
  "fingerprint": {
    "unf": "UNF:6:sAsKNmjOtnpJtXi3Q6jVrQ==",
    "cid": "bafkreibho6naw5r7j23gxu6rzocrud4pc6fjsnteyjveirtnbs3uxemv2u"
  },
  "encoding": "UTF-8"
}
```

### JSONL technical metadata

Analysing JSONL should yield some useful information. Like many of the
analyses output by this tool this information is a work in progress and
time will tell if its useful.

#### Line length

Line length might not be a useful output for JSONL as the specification
itself determines JSONL files are very likely to have long lines. The
output is therefore disabled.

#### Fingerptinting

Fingreprinting JSONL versus standard JSON is done by treating the
JSONL file as a list of objects in memory. An important distinction to make is
that while this is technically correct, it's not structurally correct, i.e.
a JSONL file is not serialized as a list, nor, need it be deserialized into
memory as a `list` object. That being said, using a list structure in JSONID
as a small concession enabling fingerprinting makes it a convenient choice
and I hope it will prove beneficial.

#### Example JSONL analysis

JSONL analysis output is, therefore, a little more sparse than the
standard JSONID output, an example, at present, looks as follows:

```json
{
  "number_of_lines": 4,
  "fingerprint": {
    "unf": "UNF:6:iBedoWLhyVzfXOM0OcXWBg==",
    "cid": "bafkreigjgec7pbdao3ilk2pqe3tp3qg5bu426wyebnrelbm34ebhcbxs6q"
  },
  "doctype": "JSONL",
  "encoding": "UTF-8",
  "compression": "application/gzip"
}
```

## Utils

### json2json

UTF-16 can be difficult to read as UTF-16 uses two bytes per every one, e.g.
`..{.".a.".:. .".b.".}.` is simply `{"a": "b"}`. The utility `json2json.py`
in the utils folder will output UTF-16 as UTF-8 so that signatures can be
more easily derived. A signature derived for UTF-16 looks exactly the same
as UTF-8.

`json2json` can be called from the command line when installed via pip, or
find it in [src.utils][json2json-1].

[json2json-1]: src/utils/json2json.py

## Docs

Dev docs are [available][dev-docs-1].

[dev-docs-1]: https://ffdev-info.github.io/jsonid/jsonid/

----

## Developer install

### pip

Setup a virtual environment `venv` and install the local development
requirements as follows:

```bash
python3 -m venv venv
source venv/bin/activate
python -m pip install -r requirements/local.txt
```

### tox

#### Run tests (all)

```bash
python -m tox
```

#### Run tests-only

```bash
python -m tox -e py3
```

#### Run linting-only

```bash
python -m tox -e linting
```

<!--markdownlint-disable-->

### pre-commit

Pre-commit can be used to provide more feedback before committing code. This
reduces reduces the number of commits you might want to make when working on
code, it's also an alternative to running tox manually.

To set up pre-commit, providing `pip install` has been run above:

* `pre-commit install`

This repository contains a default number of pre-commit hooks, but there may
be others suited to different projects. A list of other pre-commit hooks can be
found [here][pre-commit-1].

[pre-commit-1]: https://pre-commit.com/hooks.html

## Packaging

The [`justfile`][just-1] contains helper functions for packaging and release.
Run `just help` for more information.

[just-1]: https://github.com/casey/just

### pyproject.toml

Packaging consumes the metadata in `pyproject.toml` which helps to describe
the project on the official [pypi.org][pypi-2] repository. Have a look at the
documentation and comments there to help you create a suitably descriptive
metadata file.

### Versioning

Versioning in Python can be hit and miss. You can label versions for
yourself, but to make it reliaable, as well as meaningful is should be
controlled by your source control system. We assume git, and versions can
be created by tagging your work and pushing the tag to your git repository,
e.g. to create a release candidate for version 1.0.0:

```sh
git tag -a 1.0.0-rc.1 -m "release candidate for 1.0.0"
git push origin 1.0.0-rc.1
```

When you build, a package will be created with the correct version:

```sh
just package-source
### build process here ###
Successfully built python_repo_jsonid-1.0.0rc1.tar.gz and python_repo_jsonid-1.0.0rc1-py3-none-any.whl
```

### Local packaging

To create a python wheel for testing locally, or distributing to colleagues
run:

* `just package-source`

A `tar` and `whl` file will be stored in a `dist/` directory. The `whl` file
can be installed as follows:

* `pip install <your-package>.whl`

### Publishing

Publishing for public use can be achieved with:

* `just package-upload-test` or `just package-upload`

`just-package-upload-test` will upload the package to [test.pypi.org][pypi-1]
which provides a way to look at package metadata and documentation and ensure
that it is correct before uploading to the official [pypi.org][pypi-2]
repository using `just package-upload`.

<!--markdownlint-enable-->

[pypi-1]: https://test.pypi.org
[pypi-2]: https://pypi.org