The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for js-build-cli 0.0.6
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 | |
|---|---|---|---|---|
| js-build-cli-0.0.6.tar.gz | 10.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| js_build_cli-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.5 kB
Release files / js-build-cli-0.0.6.tar.gz
| Download URL | js-build-cli-0.0.6.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9364275db01485b039a135b14e963ed8fed567b35d6798d04082923779ce0ee0
|
|
BLAKE2b-256 checksum How to use checksums |
d2d60654069e6463ee2094372888e1a7c3c5c02f49a71b83f4d9c4e85cc77884
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Release files / js_build_cli-0.0.6-py3-none-any.whl
| Download URL | js_build_cli-0.0.6-py3-none-any.whl |
|---|---|
| Size | 10.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc9526ac3b8da40617af6d4acb970d327f48b5f4fa6776efd3539f4f72a93fcb
|
|
BLAKE2b-256 checksum How to use checksums |
f3d06cd350dfa710963415c26ad16aea4bb7afba64cf4b5a21d1a1e41c55086e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for js-build-cli 0.0.6
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.
