The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for mmasim-kernels 2.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 | |
|---|---|---|---|---|
| mmasim_kernels-2.1.1.tar.gz | 54.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mmasim_kernels-2.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 119.7 kB
Release files / mmasim_kernels-2.1.1.tar.gz
| Download URL | mmasim_kernels-2.1.1.tar.gz |
|---|---|
| Size | 54.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58134e9f010e02058b930d1f7c9405fa89e14fde9dc40edfc07c1c0495fcec0f
|
|
BLAKE2b-256 checksum How to use checksums |
afcf44c2a4bbed768b2539579ffa4082ee56e2af59e6c8821673b566bbc28170
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / mmasim_kernels-2.1.1-py3-none-any.whl
| Download URL | mmasim_kernels-2.1.1-py3-none-any.whl |
|---|---|
| Size | 65.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6ac2679dee64315bd821d06ea17cf9ce3f1fb75f96cff31354e02d38bf572dd4
|
|
BLAKE2b-256 checksum How to use checksums |
bf53a869f43a3d47e6db3c0bdf64f9622cf39ffa98ed38ca597b4cfa4898319a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Security for mmasim-kernels 2.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.
