1 maintainer
Metadata
1 maintainer
Release files for pidevkit-coding-agent 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 | |
|---|---|---|---|---|
| pidevkit_coding_agent-0.1.0.tar.gz | 36.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pidevkit_coding_agent-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 85.9 kB
Release files / pidevkit_coding_agent-0.1.0.tar.gz
| Download URL | pidevkit_coding_agent-0.1.0.tar.gz |
|---|---|
| Size | 36.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba114c0e48db338a02720d1d8c2ae07bbee643dde4be96fc8a62067389113fb7
|
|
BLAKE2b-256 checksum How to use checksums |
341c716f6b5df515fe72e00a45e3dfda4a6f1a2c9ff0e013c46e285f6bdf5d3d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.3
|
Release files / pidevkit_coding_agent-0.1.0-py3-none-any.whl
| Download URL | pidevkit_coding_agent-0.1.0-py3-none-any.whl |
|---|---|
| Size | 49.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
701b83eec1c3fb675a4a23dfa06b5708b7a8696373cecc2ef033e89bdc8455cf
|
|
BLAKE2b-256 checksum How to use checksums |
375294c2bc8e27cb12af2b47e61d49e9872dc4fcf07ce246c9a57a0e447a8137
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.3
|
Security for pidevkit-coding-agent 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.
