The author of this package has not provided a project description
Metadata
Release files for materializer 0.1.0
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 | |
|---|---|---|---|---|
| materializer-0.1.0.tar.gz | 1.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| materializer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.9 kB
Release files / materializer-0.1.0.tar.gz
| Download URL | materializer-0.1.0.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
12b4475062d5b7648b3c5560efea7cda091b6e9169c8ca19e1c8f685a31f7dc4
|
|
BLAKE2b-256 checksum How to use checksums |
4cf2e70dbbb7de09ed764f65b3fad6631e07aae32f5d5774955e1de6c9e15525
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / materializer-0.1.0-py3-none-any.whl
| Download URL | materializer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9f1e775b3c43a805322e741b1e7e85cc748fb6623bd4883a5025c8b204214cb
|
|
BLAKE2b-256 checksum How to use checksums |
66d9634d14b6e23e3ee85e5151b8bfcd162fdbd9804c8fee1b3ae9aca79d6b33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for materializer 0.1.0
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.