Query result

Key	Value
FileName	./usr/bin/pip-missing-reqs
FileSize	997
MD5	89DE0F3D66D65D87F6B74266015DD3F9
SHA-1	A3999B77834FDBF79C53D786770EA1EA01DC3AC4
SHA-256	63BC29292A858E46EB75F41E9AB141674F0367D5F241FC84F9AF51A90F99DB3C
SSDEEP	24:PuPO+ZFt9T9LwKLPLwoZZT0EeC0RDajxAv:GPHphsmsoZZTIas
TLSH	T1E711ED929821F752A6C187DE3CF061AA022758A377902025F5DC8BF45FC43105C36F14
hashlookup:parent-total	1
hashlookup:trust	55

Network graph view

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
FileSize	14100
MD5	579D1EC23DF6096B07916F796C025360
PackageDescription	checker 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.
PackageMaintainer	Francois Marier <francois@debian.org>
PackageName	pip-check-reqs
PackageSection	devel
PackageVersion	2.3.0-1
SHA-1	25F609838B95FAE9EDCE0B11DED5FFECC2D0B504
SHA-256	CC33856707198A684C6A0F011B7BA7B1F4D6E52704E0F3F1A3F289191A614137