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