The author of this package has not provided a project description
Metadata
Release files for arg.sqlutility 1.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 | |
|---|---|---|---|---|
| arg.sqlutility-1.0.tar.gz | 14.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arg.sqlutility-1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.5 kB
Release files / arg.sqlutility-1.0.tar.gz
| Download URL | arg.sqlutility-1.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97b45c6d6eb88d568ab25300d332baca27dba5915bb70b12ab99d395c7ed4e22
|
|
BLAKE2b-256 checksum How to use checksums |
a6025c25e460125aa8a88fb19697f50fd43a30eab5271e4a4bbb7b1fd1c2f9a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / arg.sqlutility-1.0-py3-none-any.whl
| Download URL | arg.sqlutility-1.0-py3-none-any.whl |
|---|---|
| Size | 15.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
368d3f2f98c560f8583f32763a2e58eff3b87e5f68c2ab24da88d0af03d32329
|
|
BLAKE2b-256 checksum How to use checksums |
c68b1ca12bd1bd6b9532dbc95dba9865b0166d2c834613e11944a6c14c56d903
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for arg.sqlutility 1.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.