Result for 3594CF9820E92DA4B978B6D68F96E6070EEF2855

Query result

Key Value
FileName./usr/share/man/man3/Test::Perl::Critic::Progressive.3pm.xz
FileSize4356
MD512BD6C070DEA2736D811878A0FAE6679
SHA-13594CF9820E92DA4B978B6D68F96E6070EEF2855
SHA-256FFED4C286DA10AC21785D75C3A978AD3D959A30DAE844B72CF75B25F4CC2926A
SSDEEP96:9ON6rsCsoq1vgIFi0AOAhX3aV6g+EEaFOf4+i2EIYqEnSB04Q:ANB5oq9JK9aAzENmrESBDQ
TLSHT13C918DA0BE06D8D7C53DD403F15440E0E50532D2AA38E27648CD9F2AA57EC2D44CCEAD
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
MD50C8802CB8BB01DE73D635B04E2FF1311
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
PackageRelease8.mga7
PackageVersion0.30.0
SHA-174BF21BCE76FC17CE5B1C1698685678291C6CF16
SHA-2564162BB0DADDF06E6CBFC9931E1691EE2C37115B57EDE52DF1A645D731052EA24