Result for B8C464CC013D8EA0656E38CCD87A478E54EF734B

Query result

Key Value
FileName./usr/share/man/man3/Test::Perl::Critic::Progressive.3pm.xz
FileSize4356
MD5E0CD2C56C24826B57DCD75B3F4FD710F
SHA-1B8C464CC013D8EA0656E38CCD87A478E54EF734B
SHA-25665196D952A7B40C5B91F776AD46C437F67A22030C0B0741838E0ACAF3E964EA6
SSDEEP96:9ONCDtY11YufggfWhklWVWpmPGDmAMKDy0PWR/IP+xcDBgj:ANStY1xggfWhkw2HzDPWxymcC
TLSHT1C6917D03E695C5963BFC949246CC9862BEC99CCFE7338053D810751966AF71A0FF5C01
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
MD58C28FEECC62F2E4DEC173006741B1177
PackageArchnoarch
PackageDescriptionApplying coding standards to large amounts of legacy code is a daunting task. Often times, legacy code is so non-compliant that it seems downright impossible. But, if you consistently chip away at the problem, you will eventually succeed! Test::Perl::Critic::Progressive uses the the Perl::Critic manpage engine to prevent further deterioration of your code and *gradually* steer it towards conforming with your chosen coding standards. The most effective way to use Test::Perl::Critic::Progressive is as a unit test that is run under a continuous-integration system like CruiseControl or AntHill. Each time a developer commits changes to the code, this test will fail and the build will break unless it has the same (or fewer) Perl::Critic violations than the last successful test. See the the "NOTES" manpage for more details about how this test works.
PackageMaintainerumeabot <umeabot>
PackageNameperl-Test-Perl-Critic-Progressive
PackageRelease9.mga8
PackageVersion0.30.0
SHA-10EC3FB6C142DDD5D498230244FAA928970806833
SHA-2568F5B0259101B24D13209C24325A5213A7FF85660A500B858BB72D6BA07DAC873