The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for atomery 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 | |
|---|---|---|---|---|
| atomery-0.0.1.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atomery-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.9 kB
Release files / atomery-0.0.1.tar.gz
| Download URL | atomery-0.0.1.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6c0b057a2163ecb34036a9c6b9c450dfaf275121c4973e08a15a37701a97846
|
|
BLAKE2b-256 checksum How to use checksums |
afa02cb9ebe8eb40d5180e5e4583dd8619057bf09bbc0e6164a3fc9ab695b2c1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / atomery-0.0.1-py3-none-any.whl
| Download URL | atomery-0.0.1-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
59f352f5ce696fb10ebfe259cc37600a41f4e0d787d549f1f1dce5bb6df06442
|
|
BLAKE2b-256 checksum How to use checksums |
1971da4edf6babd50d3e305867def958000b3cc8b358fe334cc3c8065839641c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for atomery 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.
