1 maintainer
Metadata
1 maintainer
Release files for tahoe-scorm 0.2.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 | |
|---|---|---|---|---|
| tahoe-scorm-0.2.0.tar.gz | 3.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tahoe_scorm-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.6 kB
Release files / tahoe-scorm-0.2.0.tar.gz
| Download URL | tahoe-scorm-0.2.0.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b046c1a47c93f2bdb31f44b253eb0dc7af777f42ca4ffd3b82a3cdff457516a8
|
|
BLAKE2b-256 checksum How to use checksums |
99948010f0c44c8917b0139a1473ae0e6e5702b9ac3c54e566ab19ff538e8286
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Release files / tahoe_scorm-0.2.0-py3-none-any.whl
| Download URL | tahoe_scorm-0.2.0-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26257d170786921dffcce362090d9749437e9c4ba0f704ec3fb341479c35a27d
|
|
BLAKE2b-256 checksum How to use checksums |
267fbff2eec4d670fad2d7cd4aed732098e442815f97a025d0b287f88b374cce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Security for tahoe-scorm 0.2.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.
