1 maintainer
Metadata
1 maintainer
Release files for codesecdirectmit 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 | |
|---|---|---|---|---|
| codesecdirectmit-0.1.0.tar.gz | 2.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codesecdirectmit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.6 kB
Release files / codesecdirectmit-0.1.0.tar.gz
| Download URL | codesecdirectmit-0.1.0.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
883004c705b2087fe2bbd61c01b335408983e9508eddaa66f0abe01096565175
|
|
BLAKE2b-256 checksum How to use checksums |
672586a6ed60827b385fcba70ad563ae6fbaa8e90b1c14f72a7601e4c620d782
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Release files / codesecdirectmit-0.1.0-py3-none-any.whl
| Download URL | codesecdirectmit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
efb99cdfa2cef0aedb41d3c6cdcbceabf7e6afaba5262e8046c2784c018b766f
|
|
BLAKE2b-256 checksum How to use checksums |
28191fed0121bb225e3d4d53aaf09075138bf692287afb7bbefa5af160bd46ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.8.10
|
Security for codesecdirectmit 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.
