The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for strictacode 0.0.12
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 | |
|---|---|---|---|---|
| strictacode-0.0.12.tar.gz | 139.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| strictacode-0.0.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 212.2 kB
Release files / strictacode-0.0.12.tar.gz
| Download URL | strictacode-0.0.12.tar.gz |
|---|---|
| Size | 139.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c18884145aebd46dbbba61f26c6615ab7b7c4cd7e171130abd340da36ddb28b6
|
|
BLAKE2b-256 checksum How to use checksums |
5251c4c877f57ae3abda6f56233806e0ca549c703e64bffa3f751e05f2189ffd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / strictacode-0.0.12-py3-none-any.whl
| Download URL | strictacode-0.0.12-py3-none-any.whl |
|---|---|
| Size | 73.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
644070fbda875d9a19e5484729b22ebe03cbed74c0872c15b326f5a4b672c33a
|
|
BLAKE2b-256 checksum How to use checksums |
2dd4a193f968428f2d71dbedd4b6db49203738e571aa012fd0e060f3c6b84bf1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for strictacode 0.0.12
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.
