Noggin messages
A schema package for Noggin.
See the detailed documentation on packaging your schemas.
Metadata
Release files for noggin-messages 1.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 | |
|---|---|---|---|---|
| noggin_messages-1.1.0.tar.gz | 6.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| noggin_messages-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / noggin_messages-1.1.0.tar.gz
| Download URL | noggin_messages-1.1.0.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78ce070a0c7b89824eef97ee79773681832bfc1b2eb7737845d7eb0d97dec730
|
|
BLAKE2b-256 checksum How to use checksums |
769ce028ac26067b4dbd9d8cc9e744ed94640d867540cf5081143502fa032ebb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Release files / noggin_messages-1.1.0-py3-none-any.whl
| Download URL | noggin_messages-1.1.0-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c6d049ade672eac0aa81a1dba3f425235af03730a1a603dc728878b35833fdc3
|
|
BLAKE2b-256 checksum How to use checksums |
96b6b20801f0b6e13c0d83e21530d11584e2b39d80a661f33c563372b48d78fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Security for noggin-messages 1.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.