Metadata
Release files for projen-publishing-tester 0.0.2
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 | |
|---|---|---|---|---|
| projen_publishing_tester-0.0.2.tar.gz | 14.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| projen_publishing_tester-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.8 kB
Release files / projen_publishing_tester-0.0.2.tar.gz
| Download URL | projen_publishing_tester-0.0.2.tar.gz |
|---|---|
| Size | 14.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d0db01f45281c476613aae9a0ec55e8e348ed2ad540a39437e7af8fcdda0b51
|
|
BLAKE2b-256 checksum How to use checksums |
74968251d49246a4d6a8512f16854f5446e3013c66b1e418847737c6c4bb27ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Release files / projen_publishing_tester-0.0.2-py3-none-any.whl
| Download URL | projen_publishing_tester-0.0.2-py3-none-any.whl |
|---|---|
| Size | 14.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c26cc3e43272ea9b4ac548c09f67c5ab6d279a43aa73bbfe9fc9250f9fc31f7
|
|
BLAKE2b-256 checksum How to use checksums |
400e5d072d09da9771b348e01da65403819b4fa2159527cb8380a80d48c3cd1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Security for projen-publishing-tester 0.0.2
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.