Query result

Key	Value
FileName	./usr/share/doc/pip-check-reqs/changelog.gz
FileSize	1251
MD5	9766789F09B8AB7B1446B9402015B1DE
SHA-1	7B7B956CE027D0826A10765BE2DA802AF30C96EC
SHA-256	71D9DD1B68330DA1432EEE0B0EC1ECCE17CC9B7BA6244E7940A7BB7B59FD8202
SSDEEP	24:XvroT7oyiSKVHvU567w3yId8yAnN3dJJr2Bvk3wEoVBAZrtM:Xv0nTiS0Hvw67xIHw3Jq5kdfZ5M
TLSH	T1D821EA1583C8F7A6B69542D23AFB36767145803A0CF460D5D01BED70BFBD0A04AA7DB6
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