1 maintainer
Metadata
1 maintainer
Release files for batchcensusgeocode 0.0.7
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 | |
|---|---|---|---|---|
| batchcensusgeocode-0.0.7.tar.gz | 29.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| batchcensusgeocode-0.0.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.7 kB
Release files / batchcensusgeocode-0.0.7.tar.gz
| Download URL | batchcensusgeocode-0.0.7.tar.gz |
|---|---|
| Size | 29.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24a94a7bb8960a1bd727713affa09e5809f2dd88b1e9542c7f0f7f6bbc9e2cc5
|
|
BLAKE2b-256 checksum How to use checksums |
da05b3904c2fa3e0fc5ae3e55926af1a7797333da8c38742902b8318ba169c33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Release files / batchcensusgeocode-0.0.7-py3-none-any.whl
| Download URL | batchcensusgeocode-0.0.7-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
08a1bc93d94a69287ee2771d0ba516b097b02947d68240ae2bae9b3e9bddb1d9
|
|
BLAKE2b-256 checksum How to use checksums |
9699e9b036662af80569bddbeab76087448fff85c4706c09b4393fb491c817ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.11
|
Security for batchcensusgeocode 0.0.7
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.
