1 maintainer
Metadata
1 maintainer
Release files for inferencemax 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 | |
|---|---|---|---|---|
| inferencemax-0.0.1.tar.gz | 4.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inferencemax-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.0 kB
Release files / inferencemax-0.0.1.tar.gz
| Download URL | inferencemax-0.0.1.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
742a5100a22ef7d4dd9e179229410d80edf7fe641b0f30ce976cf0e9f07460c4
|
|
BLAKE2b-256 checksum How to use checksums |
333b14c1893234620d3a86af858b10b79fc20eaa55e8a264adc55d1a70d57823
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.3 Linux/6.8.0-45-generic
|
Release files / inferencemax-0.0.1-py3-none-any.whl
| Download URL | inferencemax-0.0.1-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2eab44c82d6e94f92e9b2b5474bf9225b80269a2c713f895109b266b9a656db
|
|
BLAKE2b-256 checksum How to use checksums |
89073f7aea823b19ef7249de110275f1b25aca923908c0502add99bef6d16237
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.3 CPython/3.12.3 Linux/6.8.0-45-generic
|
Security for inferencemax 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.
