Existpy
CLI tool for checking if a given project name exists in pipy.
Installation
>>> pip install existpy
Example
>>> existpy [packagename] TITLE VERSION DESCRIPTION -------------------------------------------------- [packagename-like] [version] [packagename-like] [version] >>> >>> existpy [packagename] --summary TITLE VERSION DESCRIPTION -------------------------------------------------- [packagename-like] [version] [description] [packagename-like] [version] [description]
LICENSE
UPDATES
26/9/2019 Add option for possible solution, if pypi has a suggestion.
For example
>>> existpy [packagename-with-typo] There were no results for [packagename-with-typo] Did you mean [other-packagename] ?
1 maintainer
Metadata
1 maintainer
Release files for existpy 0.0.2
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 | Actions |
|---|---|---|---|---|
| existpy-0.0.2.tar.gz | 2.7 kB | Without provenance | Details for existpy-0.0.2.tar.gz |
Release files / existpy-0.0.2.tar.gz
| Download URL | existpy-0.0.2.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20efbcc3886e145db884b7d0ea9c57c8fd3c6a2fccab2fea032eef14c231e53b
|
|
BLAKE2b-256 checksum How to use checksums |
f36f2a9c66a81c8fcbb07c85d12620b706f6e4d4fa34fbadde9eee253fd1092a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.4
|
Security for existpy 0.0.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
