The author of this package has not provided a project description
Metadata
Release files for counter-assignment 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 | |
|---|---|---|---|---|
| counter-assignment-0.1.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| counter_assignment-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.2 kB
Release files / counter-assignment-0.1.tar.gz
| Download URL | counter-assignment-0.1.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e31b1629579bea67b9f439b79aedc32e7253cf236db15a0c0238e96d0fb9808
|
|
BLAKE2b-256 checksum How to use checksums |
75a6dff2f2d2249fa58b5fe42540c1b2a11b5c864654e65ee620182bad82be15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.9
|
Release files / counter_assignment-0.1-py3-none-any.whl
| Download URL | counter_assignment-0.1-py3-none-any.whl |
|---|---|
| Size | 1.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
876540d8aac9673aa958a5e97167d15169f8a5d94939e2246706bb84c3ea2745
|
|
BLAKE2b-256 checksum How to use checksums |
0bf4b2cfd48cd43bb96e3982e5e6eeedc82d12b556929a840fbe1d4b34f3d86a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.9
|
Security for counter-assignment 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.