Result for 2C42096F67783442790ED350B9C822C19DF89F72

Query result

Key Value
FileName./usr/share/doc/pip-check-reqs/changelog.Debian.gz
FileSize430
MD51D6B94F60093B42EE3E67E2850A115C4
SHA-12C42096F67783442790ED350B9C822C19DF89F72
SHA-25607A823E65C60FB4346C9E6272A7585C4ECD40C7418162471DE01EDFC35CACABD
SSDEEP12:XZWEPhu11OSKJhq517/y6NHM6794JsfQ9REHp:XoEPhu11EW517vRMW4QQ9op
TLSHT1E8E0ABA4AF16A069C91006F29CD30518DFA729C46579AFEC06D522B93FBF6A62502C83
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