The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for temporal-assessment 0.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 | |
|---|---|---|---|---|
| temporal_assessment-0.0.1.tar.gz | 936 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| temporal_assessment-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 kB
Release files / temporal_assessment-0.0.1.tar.gz
| Download URL | temporal_assessment-0.0.1.tar.gz |
|---|---|
| Size | 936 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cacd955f2255e90cb49b7dca5d18bad681a1f68eb1b599d3eca6d94f7290387d
|
|
BLAKE2b-256 checksum How to use checksums |
d630adf71aedf6267bc93bc8e22c615e5496c9368f64886622ffa256cf927cf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.22
|
Release files / temporal_assessment-0.0.1-py3-none-any.whl
| Download URL | temporal_assessment-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
424fc96f767253006af63019ce01f8ea74bdc2708b72fdd9240bdd307357270f
|
|
BLAKE2b-256 checksum How to use checksums |
4415b8a5b692967d501f0b881729cfc3d66f3c007f4fd65b591fe776b7f3fa47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.22
|
Security for temporal-assessment 0.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.
