The author of this package has not provided a project description
Metadata
Release files for codon-model 0.0.6
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 | |
|---|---|---|---|---|
| codon_model-0.0.6.tar.gz | 164.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codon_model-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 367.4 kB
Release files / codon_model-0.0.6.tar.gz
| Download URL | codon_model-0.0.6.tar.gz |
|---|---|
| Size | 164.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
26a7fc130d948c997481e915ab0b4b399abd82f97918a8d450ff6178587e9884
|
|
BLAKE2b-256 checksum How to use checksums |
ec769f7513414c02ab79392ccbb1b8088581f3cd6c20231db69853be1412ccb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / codon_model-0.0.6-py3-none-any.whl
| Download URL | codon_model-0.0.6-py3-none-any.whl |
|---|---|
| Size | 203.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b5031378874496c746baded00334a8ff4bb86bdb8c01f2436aef9355c0b56a6f
|
|
BLAKE2b-256 checksum How to use checksums |
c3122a7f158d967e9e51fa02a02404d95f51014f52e8c8b86bc6089fa827d0db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for codon-model 0.0.6
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.