Result for 53F5BF2A5F7DD357EA5B4210B5663C1355859E25

Query result

Key Value
FileName./usr/bin/pip-extra-reqs
FileSize993
MD5CA595763C53061435FDE0DFA432445EC
SHA-153F5BF2A5F7DD357EA5B4210B5663C1355859E25
SHA-2561F6AD0494DB0C160920EEBC1B8BAB2D4F7BF8207FB34DD08C600E4AAA4F8A1BA
SSDEEP12:HsKuPQA2Day8gQ9DAOVD8FuRwKlIE008F+RwK9VrLpA0zFFLOg6SXwQ0EeC9KRQU:PuPOmFt9T9LwKLPLwoZZT0EeC0RDajxE
TLSHT18F1110929862F252A6C187DA3CF0616A12274CA377902025F5CC8BF45FC43105C36F14
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize14100
MD5579D1EC23DF6096B07916F796C025360
PackageDescriptionchecker for missing and extra packages in Python requirements It happens: you start using a module in your project and it works and you don't realise that it's only being included in your virtualenv because it's a dependency of a package you're using. pip-missing-reqs finds those modules so you can include them in the requirements.txt for the project. . Alternatively, you have a long-running project that has some packages in requirements.txt that are no longer actively used in the codebase. The pip-extra-reqs tool will find those modules so you can remove them.
PackageMaintainerFrancois Marier <francois@debian.org>
PackageNamepip-check-reqs
PackageSectiondevel
PackageVersion2.3.0-1
SHA-125F609838B95FAE9EDCE0B11DED5FFECC2D0B504
SHA-256CC33856707198A684C6A0F011B7BA7B1F4D6E52704E0F3F1A3F289191A614137