The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for oslabcode 1.0.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 | |
|---|---|---|---|---|
| oslabcode-1.0.0.tar.gz | 5.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oslabcode-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.2 kB
Release files / oslabcode-1.0.0.tar.gz
| Download URL | oslabcode-1.0.0.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9fd101a5d0c61c5d69f86b3778b14d4f3fe5737cb115896b2f87bbbc86c1e9b
|
|
BLAKE2b-256 checksum How to use checksums |
60f33e6335547356ec61612367b60c66e8932106b0d0a74d76242e28523144cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / oslabcode-1.0.0-py3-none-any.whl
| Download URL | oslabcode-1.0.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ecb1ab246883dbe68bb1760723896f329d36a35121922690e9ab9971da8666e
|
|
BLAKE2b-256 checksum How to use checksums |
6a9597413273347a97d48a6e60ace96c3d6dbf83c5d356d1e63c75084bd36586
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for oslabcode 1.0.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.
