The author of this package has not provided a project description
Metadata
Release files for compound-thinking 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_thinking-0.0.1.tar.gz | 489 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| compound_thinking-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.6 kB
Release files / compound_thinking-0.0.1.tar.gz
| Download URL | compound_thinking-0.0.1.tar.gz |
|---|---|
| Size | 489 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
98e95910d89b512ea4215a68a1a64d252822fc74f59c60e211015396e4ba35fe
|
|
BLAKE2b-256 checksum How to use checksums |
1995f873cc357cfa905d875e73347bebdd0f22a6716fa6d4b29cdbc20171dbe2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Release files / compound_thinking-0.0.1-py3-none-any.whl
| Download URL | compound_thinking-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
342a1655548157e971a737754ac3e5eac130cf7ec17b14fb7c0ca7bb9992ff55
|
|
BLAKE2b-256 checksum How to use checksums |
a4ff5c23e419796e9ec9661695866fbd8a6bb21aaee2d6d61aeda6d7d0bb9dd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.2
|
Security for compound-thinking 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.