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