The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for orcapod-core 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 | |
|---|---|---|---|---|
| orcapod_core-0.0.1.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| orcapod_core-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.6 kB
Release files / orcapod_core-0.0.1.tar.gz
| Download URL | orcapod_core-0.0.1.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be12207cfe21c647fa2de5686ab9d26d1e74e3ee3a2df46506f6c9763d5e6f25
|
|
BLAKE2b-256 checksum How to use checksums |
d5eb2c9c1274b8e2ce17c08351dcadb8d94c6194f8311e7f9b0118504678b9c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / orcapod_core-0.0.1-py3-none-any.whl
| Download URL | orcapod_core-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
30b9c55cec1962775f42b31b0da97ae73e5c9e52918374b16823158f03181f71
|
|
BLAKE2b-256 checksum How to use checksums |
040185f7661c2c15fa69385eb8ea0088ed1b3b943ee8905e7b943b0d6a0be6ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for orcapod-core 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.
