rigour
Data cleaning and validation functions for processing various types of text emanating and describing the business world. This applies to human and company names, language, territory and country codes, corporate and tax identifiers, etc.
The underlying idea is that handling these sorts of descriptors is easy on first glance, but reveals a dizzying set of complexity when carried into production. This is why rigour consolidates implementations that have already met some edge cases and are well-tested.
Installing rigour
You can grab the latest release from PyPI:
pip install -U rigour
Usage & documentation
See: https://rigour.followthemoney.tech/
Acknowledgements
The address formatting database contained in rigour/data/addresses/formats.yml is derived from worldwide.yml in the OpenCageData address-formatting repository. It is used to format addresses according to customs in the country that is been encoded.
rigour consolidates and includes a set of older Python libraries into a single codebase: languagecodes, pantomime, fingerprints. The development of these libraries was funded by OCCRP as part of the Aleph software project.
License
MIT. See LICENSE.
2 maintainers
Metadata
2 maintainers
Release files for rigour 2.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| rigour-2.6.0.tar.gz | 5.2 MB | With provenance | Details |
Built distributions (wheels)
Total release size: 231.5 MB
Release files / rigour-2.6.0.tar.gz
| Download URL | rigour-2.6.0.tar.gz |
|---|---|
| Size | 5.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8914bf1498391e1f7e1b77653515ad5d42b347142d467fc40abd5500fecbba9
|
|
BLAKE2b-256 checksum How to use checksums |
dadea15ff219a6347ed2ef930e9ba982f0e0df1675f6c90f7fe8d9514d1cae0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp314-cp314-win_amd64.whl
| Download URL | rigour-2.6.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9e4eb7b9be322803a264f35721180ed2fbc044ff5eb286481e1525635835458a
|
|
BLAKE2b-256 checksum How to use checksums |
141aa699281ac33e3a1ddf0834f84fca9160a67f195971fe76ab8c2881e317cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | rigour-2.6.0-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.8 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
3f1079ebcf14c3daa00430d9de38749542b1f9e7b82029baa7ac4d2f31e09116
|
|
BLAKE2b-256 checksum How to use checksums |
267f99de0f25c99ed30e0fcc037a83b5c6ab761e8d2bd2a279ae264ebf9ec02e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | rigour-2.6.0-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.7 MB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
b2eb3d947279c829bdaf98c80bab0acc54be5417f0f02cd3f0f22544e952a05e
|
|
BLAKE2b-256 checksum How to use checksums |
36d184e953bd1e83c5904f7a7cc91740666922bf5d05ac156968de6faa9a0bdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rigour-2.6.0-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
941598a2293c7635c509ece9c9e40c9aa4d9217473132188690fe1cbda3970ed
|
|
BLAKE2b-256 checksum How to use checksums |
52743d4be7b745c370e5f585f84ad941961ff962508e46f375cf43203b644b81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | rigour-2.6.0-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
8045716a54c81cd0f717ea77521f08e2162a5c7a16a1fbfae2b504bcff21d925
|
|
BLAKE2b-256 checksum How to use checksums |
be734aeb0f0f158cf54b0d9fc3bc4e66dd843bdedb968dc4443c745b689213a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | rigour-2.6.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
70953b02e4e126fdf8fddba47a14c0c9a2828002daad6777c18d1b8b24230976
|
|
BLAKE2b-256 checksum How to use checksums |
23431297c3eb0769dd92b58b67a36445808e68269a62abeed402b96dbe83b905
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp314-cp314-macosx_10_12_x86_64.whl
| Download URL | rigour-2.6.0-cp314-cp314-macosx_10_12_x86_64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.14 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
088c73494ef3aaefa75159357f6546fc8b714e28f9a64cde2388d355c7acbebd
|
|
BLAKE2b-256 checksum How to use checksums |
f415a91a5c5c4e6a54d96f8baa73cc9f85b663cb7701eb84a3d73569969a522e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp313-cp313-win_amd64.whl
| Download URL | rigour-2.6.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
a8586da33b37f16071a853b9591596e30b3233da034856157bfff9c8632986d0
|
|
BLAKE2b-256 checksum How to use checksums |
51d4110879f560d14533d22f47c27a476dc6ac749350a1fecd9c7b281f0bdecb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | rigour-2.6.0-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.8 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
e6c91d1c850110cb9352574a9f9ad11cc9d9d79f07d5f79fe64671a39f13338d
|
|
BLAKE2b-256 checksum How to use checksums |
3de971b491f8e983972de440abaf7d7dcfa09c51c7a7148c435f58d00c3a00c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | rigour-2.6.0-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.7 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
4359c47c2b61a1b9f6db1f2fe07fae1a5b26c2c9b1ec4c434c9134e5126b45ed
|
|
BLAKE2b-256 checksum How to use checksums |
ba7203bc8ecb9632100ed6493db79f3198b0a7a92f621902855bce34a321f732
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rigour-2.6.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
69b9859e66909bee8aa8d672b49fdc2aa15cca02e6edf3dda66e90e38987906b
|
|
BLAKE2b-256 checksum How to use checksums |
01ca7880df566a7a0fe7168f640d6548672273369b0c36f2ef046926f5654ab8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | rigour-2.6.0-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
ecd518c0513d8799f69d0d2b46dea46b931b0fbe80190632648f69a9449e9d08
|
|
BLAKE2b-256 checksum How to use checksums |
9e246616d8d7124584fa01811c364ece7ca58631cccb2ad6854e28f0a32f6846
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | rigour-2.6.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8b7bea3cc1161b4c90d6a0dda8acd4dd1bdfe3bcd5faf07f3480aa9d314dfcdf
|
|
BLAKE2b-256 checksum How to use checksums |
bb346a3230c7d83ec44a5ac31aee9bc9f575c1a8cfd41b0f11bbc778bc698c76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp313-cp313-macosx_10_12_x86_64.whl
| Download URL | rigour-2.6.0-cp313-cp313-macosx_10_12_x86_64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.13 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
eb88430c5e696b520232f589b84f7de042f70401e1f9f46942af14d30839ee18
|
|
BLAKE2b-256 checksum How to use checksums |
a9caf8ff1e4aebfc2dc1f48b590dcb707dfc325a21ecde2ea3b254ad2684ea91
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp312-cp312-win_amd64.whl
| Download URL | rigour-2.6.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
bcf7b1cd8f370482db2e5016b9fe1e67f4bdd1bb1a5b830f947e8c1697678693
|
|
BLAKE2b-256 checksum How to use checksums |
b1aba17b7828fc959d6669665b16c48a153f52d3dbcc8de3504a9ddb62e40a6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | rigour-2.6.0-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.8 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
a76d51119f275da70c9fe5d3d08d3b667275fd094c3b6cb87f3a081986e5701c
|
|
BLAKE2b-256 checksum How to use checksums |
8cc1af091c43b9e26d2e84e522027fe0377909cb95af1e8905e05f8fcc8d1164
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | rigour-2.6.0-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.7 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
106281fe99ad344ee7482024702a943087009c8e5d691cc773c1dc14649bdda1
|
|
BLAKE2b-256 checksum How to use checksums |
0c76c770237298a01ecf28ba036039edb92bb64029cae92348beff534cc5abd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rigour-2.6.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
72cb3fece670010a002be6b5d0cd061a51fbfc410776b331beac5fa2e2f31563
|
|
BLAKE2b-256 checksum How to use checksums |
c992a6609eae7885f07920a68488ab94b4fbe0730745c94ef6ea9d186d78bb03
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | rigour-2.6.0-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
388dded5bd4d9dd225ee7b0890cbc501bcc60eb611ac6c921eedddb28c52aaa4
|
|
BLAKE2b-256 checksum How to use checksums |
0d04ce78f350948faf958579b19e8349143e6a699de548a8b8e695b82e996c9f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | rigour-2.6.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f1184f56ed84213107c291efac2f1e15e92f510fadcb613f6656c6c26fc03fd5
|
|
BLAKE2b-256 checksum How to use checksums |
3d252f4cd52ad5d213ec368ec319389ad74618ef1dfb42af1f6993fdce41df6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | rigour-2.6.0-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
45de44571c15422b524878df576d6681c65a8c72080a742b6cab518e78e25355
|
|
BLAKE2b-256 checksum How to use checksums |
72e2e57438a8785a60f93a5a09944172ed34190be63fca85dc849de5011554e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp311-cp311-win_amd64.whl
| Download URL | rigour-2.6.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
dd1be48e92df3e5a783ee13d6fca7a5770c22f57ae5f7f055a7a376e4f6aaeaf
|
|
BLAKE2b-256 checksum How to use checksums |
4943cfbc25723c43a5efd904d43c1bff63aa8ad43e804649fdf75f3614be17ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | rigour-2.6.0-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.8 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
3fe45ce8beb2068584e675aa94ce9b9b5ab05f6345c1fad3aefce6b5adec73c2
|
|
BLAKE2b-256 checksum How to use checksums |
7b686c83be999ea85fbac2624ffae5e420286dfddc9620b9ac2f7d9cefbc65c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | rigour-2.6.0-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.7 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
983e5cad87c86fec381f2ef983c1adef261f7b861ac80ce4a791afca22f170c3
|
|
BLAKE2b-256 checksum How to use checksums |
6f77c8b1a3b4f92e92b43028d669559596d146a41549b360d094d7de4cbc3e1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rigour-2.6.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
b4da189e3426cb41577475574303b1a584c06ec80a658302f1a6c9b76ac0e664
|
|
BLAKE2b-256 checksum How to use checksums |
b2c971f35095d0bfa77eac158da7bf42fa5f9fb45b5b551969f68c177eb52631
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | rigour-2.6.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
77091f235a97d7e2e8888ece8b5d31b5efedf586a0791ef87944d7715f55ab4d
|
|
BLAKE2b-256 checksum How to use checksums |
e9c71702ac6ad7e0b9837c72387d8b6192ac35b80da75e2959bb1604c880144a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | rigour-2.6.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
434dc17b15075fbdf56abd888e00a7f2ff45709de3a8377446414822689fc86f
|
|
BLAKE2b-256 checksum How to use checksums |
96dece20cf21d3b5d9ed8ad947f3b0ebc376e833ad38831a7408ae3caf48bebb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | rigour-2.6.0-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
5b6f34380c98dc80f8ce9efe0d0506695dd2713589f5725109108759afb90ef7
|
|
BLAKE2b-256 checksum How to use checksums |
21b59b44c352e44a04829a3486e9c421dc7e0683d6fec2874e982b3253b18bfc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp310-cp310-win_amd64.whl
| Download URL | rigour-2.6.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
26f54738e6a82db55b0a4fe1eab2f26601dfd3b4687cad3c4f2fd601ea529be7
|
|
BLAKE2b-256 checksum How to use checksums |
5983f9b807e2034f81ee02b2acfc2e1dbf99179e5bb22ddb2e70e50fd40419c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | rigour-2.6.0-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 6.8 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
422c490a4c0b86247752ccc513da960d0b623a4241d2ba088b8695afa82f86fd
|
|
BLAKE2b-256 checksum How to use checksums |
774453d8e888c0a3b734f4892b1db3094ae955e863e72222ed816d16828f7146
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp310-cp310-musllinux_1_2_aarch64.whl
| Download URL | rigour-2.6.0-cp310-cp310-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 6.7 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
0a06f7bc31cf888266c4ee34b518a335aca709c3a48d86a7932b77b328c2912b
|
|
BLAKE2b-256 checksum How to use checksums |
0e5ff9eb8797590bfbf1b346c8fd459da6438fc441805c884fd2b6e8df0157e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rigour-2.6.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
37d193cc0a760e32ce2366f0c15aa3c09cbc726a2a2524135153bc503bcc87d4
|
|
BLAKE2b-256 checksum How to use checksums |
cacc3da639514930ba5d6b8249885e8e88f590c0572f880cde85a19563ad40d6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | rigour-2.6.0-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 6.5 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
49786739e6e7cf27af1c1105e13ff9b1466e7b841eeeeb4a5c5baa35f8d7d8fd
|
|
BLAKE2b-256 checksum How to use checksums |
9ed55ce18867840724c097d50c57c7eb285f37c953034d1d7c51d6e5ef80c81c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | rigour-2.6.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a78cec04e87eadfdf83e69e401b0a823b70bcc9654a01512acad95185e35f9b5
|
|
BLAKE2b-256 checksum How to use checksums |
803d4d13ccd8ca1442431c4b7ec1fd5c466961ff4fafd32626572aea6fb17f0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / rigour-2.6.0-cp310-cp310-macosx_10_12_x86_64.whl
| Download URL | rigour-2.6.0-cp310-cp310-macosx_10_12_x86_64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | CPython 3.10 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
2e2ec1d889ac8a807b606fc0002e7eea1002332183f89c77b22b45427190ae78
|
|
BLAKE2b-256 checksum How to use checksums |
9d5157e9319c1d6ddcc69814ecd11cb5014d5201aa9c259bcd7671fb9d2252ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for rigour 2.6.0
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.
Full provenance
All 36 files in this release have been uploaded with provenance metadata.
Attestation for rigour-2.6.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA 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.
