ID32
No more ugly IDs!
ID32s look like: m6ov3liumm6trqulojtj6yselragllbg
- 32 lowercase characters of RFC 4648 Base32 (a-z2-7)
- represents 20 bytes (160 bits) of randomness
- Easily double-clickable (no hyphens or underscores)
- NanoID:
0klp0QFYiS_dOUzhF-y_g - UUID:
10dd71ca-6030-407b-89a4-55c4e11006cd - ID32:
trhfnnxkrotlcc3gluyl4mqr6aomt4e7
- NanoID:
The code is essentially the same as Nanoid, and is available for Javascript, Python and Rust.
Installation
pip install id32
Usage
from id32 import id32
id32() # h3uu3spo3skwzidi62gk6vzfr4ifxsf3
Metadata
Release files for id32 2.0.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 | Actions |
|---|---|---|---|---|
| id32-2.0.0.tar.gz | 7.4 kB | Without provenance | Details for id32-2.0.0.tar.gz |
Release files / id32-2.0.0.tar.gz
| Download URL | id32-2.0.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78946dc7b6af18bfdb6fd1713a3215a6684871e892e2e66ae0dd9d7fbac74b89
|
|
BLAKE2b-256 checksum How to use checksums |
1ffe1aa5a85fc75e6d114aecce6fce9995cde5e84d969c468f43b28f97a144cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.13.0
|
Security for id32 2.0.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.