The author of this package has not provided a project description
Metadata
Release files for python-ometa 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 | |
|---|---|---|---|---|
| python_ometa-0.0.1.tar.gz | 29.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_ometa-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 54.0 kB
Release files / python_ometa-0.0.1.tar.gz
| Download URL | python_ometa-0.0.1.tar.gz |
|---|---|
| Size | 29.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfd5c1ee15f0f6953e99c946d5a7f8828f77d04c37d4c769e750ce3381de9653
|
|
BLAKE2b-256 checksum How to use checksums |
c8c6aa85cf50f5be477b346abe87c0f1e4a069993f53c2c3e2a9172841fdaa77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.2
|
Release files / python_ometa-0.0.1-py3-none-any.whl
| Download URL | python_ometa-0.0.1-py3-none-any.whl |
|---|---|
| Size | 24.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c4fc345a9059385501365bb3cbb15ec41a0ed7a5974d83bf96bf34148275a8bb
|
|
BLAKE2b-256 checksum How to use checksums |
d050889686e8b0b8eca8d602a1c9cbdfad93957532d32735b9acff3900e08792
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.2
|
Security for python-ometa 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.