1 maintainer
Metadata
1 maintainer
Release files for agentic-conductor 0.1.0
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 | |
|---|---|---|---|---|
| agentic_conductor-0.1.0.tar.gz | 5.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agentic_conductor-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.0 kB
Release files / agentic_conductor-0.1.0.tar.gz
| Download URL | agentic_conductor-0.1.0.tar.gz |
|---|---|
| Size | 5.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
43cc15f30ff2378c6c001715df78186714940e3c88c69b4d5956858e57da81e9
|
|
BLAKE2b-256 checksum How to use checksums |
39d56b16a90664019b7bbb3e456a60a1cffc08feb88d6dbdc8734b61363a70ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Release files / agentic_conductor-0.1.0-py3-none-any.whl
| Download URL | agentic_conductor-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9b7acad9f2c905316636b51d6582925996e7a914bbc09d898e6cf317d9021ed
|
|
BLAKE2b-256 checksum How to use checksums |
d786fbf8cc1da50edf3023e223d5e8387bad5c3dc4a791c02c9b7ef35ce29386
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.2
|
Security for agentic-conductor 0.1.0
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.
