The author of this package has not provided a project description
Metadata
Release files for nbDevTools 0.0.3
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 | |
|---|---|---|---|---|
| nbdevtools-0.0.3.tar.gz | 17.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nbDevTools-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.8 kB
Release files / nbdevtools-0.0.3.tar.gz
| Download URL | nbdevtools-0.0.3.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
704ae62c133d86d80baea1b89e5e59f07fe7cb49f128d376aace910a5b12dc58
|
|
BLAKE2b-256 checksum How to use checksums |
b27df5b29cc4da43bba8e0483fc0c6fdefa5a6b86f9186ba91015b8dc118fa70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Release files / nbDevTools-0.0.3-py3-none-any.whl
| Download URL | nbDevTools-0.0.3-py3-none-any.whl |
|---|---|
| Size | 21.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b6642cc2c1e21d414f588dfa05d5e10b42566788316ae98ada63918a67e014c
|
|
BLAKE2b-256 checksum How to use checksums |
498c05a0a75564c25e8ebfa1e6a9d9d2705b783085984a5d3f4bab72042fa671
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Security for nbDevTools 0.0.3
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.