The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for js.typeahead 0.11.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 | |
|---|---|---|---|---|
| js.typeahead-0.11.1.tar.gz | 59.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| js.typeahead-0.11.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 122.4 kB
Release files / js.typeahead-0.11.1.tar.gz
| Download URL | js.typeahead-0.11.1.tar.gz |
|---|---|
| Size | 59.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee8bd96f1a427ca0270ba34ad31952f861112dd456a100bbf7a8675348fcadf6
|
|
BLAKE2b-256 checksum How to use checksums |
d8569fe1bfb633f20a2552eff2cd068362dd7ee490007d14771dde22f28e4271
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Release files / js.typeahead-0.11.1-py3-none-any.whl
| Download URL | js.typeahead-0.11.1-py3-none-any.whl |
|---|---|
| Size | 63.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9084228685189f09e2be7db8c281fe7a1f8067e590ce7673c94032f36930540f
|
|
BLAKE2b-256 checksum How to use checksums |
bd19f4b920bfc1d0d9b49924038423689c05018df3927682e07a6ace4fd14871
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for js.typeahead 0.11.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.
