Metadata
Release files for omni-api-transformer 0.1.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 | |
|---|---|---|---|---|
| omni_api_transformer-0.1.1.tar.gz | 7.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omni_api_transformer-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.6 kB
Release files / omni_api_transformer-0.1.1.tar.gz
| Download URL | omni_api_transformer-0.1.1.tar.gz |
|---|---|
| Size | 7.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
27d1d3b3ee0d22a640bfc6d5850b5e32fc74e0c320869e037258c7c3d749475e
|
|
BLAKE2b-256 checksum How to use checksums |
bc3aa56ad8264921dfaf237ae67245e80fe4de43d9d1e00683c7f85be2558f59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / omni_api_transformer-0.1.1-py3-none-any.whl
| Download URL | omni_api_transformer-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c59616f308924cfed35d2e72f12188b7bdc416a465147cac013f704bdb939ae0
|
|
BLAKE2b-256 checksum How to use checksums |
620fa8b10d61e913f4e68a84123e0c052013ccc018b6bc3581c2ce9253ba0de3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for omni-api-transformer 0.1.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.