Metadata
Release files for nbhelper-onebot 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 | |
|---|---|---|---|---|
| nbhelper_onebot-0.1.0.tar.gz | 10.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nbhelper_onebot-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.4 kB
Release files / nbhelper_onebot-0.1.0.tar.gz
| Download URL | nbhelper_onebot-0.1.0.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39eaaa5a33abf3d7ad39efd84ecfe7ed72f77ba28a27f8b1bab3036f8fc33bd1
|
|
BLAKE2b-256 checksum How to use checksums |
16906d6c0002fa93474c023e526b89576113dd0f556385957d16be3670b1bb9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
pdm/2.24.2 CPython/3.13.3 Linux/6.11.0-1015-azure
|
Release files / nbhelper_onebot-0.1.0-py3-none-any.whl
| Download URL | nbhelper_onebot-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13cbb0b4c05d490e689149f9786604339b2d366ae5be9d006c52aa5e32417da7
|
|
BLAKE2b-256 checksum How to use checksums |
9aa4f85b4e5dd8ea880c91f2ef96e70aad42d9f83c2c7819fae57bbfc6ae4ece
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
pdm/2.24.2 CPython/3.13.3 Linux/6.11.0-1015-azure
|
Security for nbhelper-onebot 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.