2 maintainers
Metadata
2 maintainers
Release files for abstract-intellect 0.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 | |
|---|---|---|---|---|
| abstract_intellect-0.0.1.tar.gz | 2.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| abstract_intellect-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 kB
Release files / abstract_intellect-0.0.1.tar.gz
| Download URL | abstract_intellect-0.0.1.tar.gz |
|---|---|
| Size | 2.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f86034ff2f4ea083fa8706d4d20340060529e38a3f4af3ceb05f3563ee49955b
|
|
BLAKE2b-256 checksum How to use checksums |
a6830b7398a48cca3ce2594e8a6d1e16ceb41069662351a01ba42898124ef913
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / abstract_intellect-0.0.1-py3-none-any.whl
| Download URL | abstract_intellect-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7c9bcad5e446d9d54a896bd490a00b3504f5f70ae4c6973cb7f5a0e0cfa5658
|
|
BLAKE2b-256 checksum How to use checksums |
4fa8fb5a5fecabcf232022d315eed925bbd947dfd734d3bb583bf1f7710f491d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for abstract-intellect 0.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.
