Metadata
Release files for at-package-scan 0.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 | |
|---|---|---|---|---|
| at_package_scan-0.1.0.tar.gz | 1.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| at_package_scan-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.8 kB
Release files / at_package_scan-0.1.0.tar.gz
| Download URL | at_package_scan-0.1.0.tar.gz |
|---|---|
| Size | 1.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6aae3d4287051fbef353d4d8f75683c1680cd850712650ff1f91a5566a4eb019
|
|
BLAKE2b-256 checksum How to use checksums |
bd702349fbbb1228554ea090a0f0b080d1a09b5347d38b2d07bee726f89d8ff4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.4
|
Release files / at_package_scan-0.1.0-py3-none-any.whl
| Download URL | at_package_scan-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
477e6651fbf3de76bf464ea4644cb55b00722f3845b2b6d88fff16ce05b66af9
|
|
BLAKE2b-256 checksum How to use checksums |
51f682d3ee8966a9921aa387f13e93db54ea3ef9a4a4a424fe2f4f34af167a7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.4
|
Security for at-package-scan 0.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.