The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for aggfindata 1.0.1
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 | |
|---|---|---|---|---|
| aggfindata-1.0.1.tar.gz | 5.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aggfindata-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.3 kB
Release files / aggfindata-1.0.1.tar.gz
| Download URL | aggfindata-1.0.1.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70a26588aa0128dc9d502dbff510af04f1b8084bbc46d148a18b3296977432da
|
|
BLAKE2b-256 checksum How to use checksums |
4425a9b94b677b78a54781872885cd9ff6cc8c9882d567a060acded27c61e7a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.13
|
Release files / aggfindata-1.0.1-py3-none-any.whl
| Download URL | aggfindata-1.0.1-py3-none-any.whl |
|---|---|
| Size | 8.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
95af65a6d16f79b69241c1082d974b265f3ec58b549ab8d488dc11a75c446d05
|
|
BLAKE2b-256 checksum How to use checksums |
bc400201a42a36c1223aa6e336dd90c52ed5899cb32d6ee1815c3037b2ebd690
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.13
|
Security for aggfindata 1.0.1
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.
