The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for compound-code 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 | |
|---|---|---|---|---|
| compound_code-0.0.1.tar.gz | 478 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| compound_code-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / compound_code-0.0.1.tar.gz
| Download URL | compound_code-0.0.1.tar.gz |
|---|---|
| Size | 478 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2741adb09f0bff28a0453616bd560e3cffa3a0175ccf49ba5bd313dc5f2b7a84
|
|
BLAKE2b-256 checksum How to use checksums |
b21684a4cd228c43f9a2749c8d7c7cedc9d1c72d6d240a03b018f9be5b56f8dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Release files / compound_code-0.0.1-py3-none-any.whl
| Download URL | compound_code-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d87f27da874679f5b50a288ad6db8a55074c6e26c2db130e11d7158dff1f0068
|
|
BLAKE2b-256 checksum How to use checksums |
8006e792d6b99ce02f5d7ad42d818c3983d957d7e9664798f8634f6e69ec4594
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Security for compound-code 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.
