Result for C9DC4E7221A225A8F727DD52E9E5EFC341364562

Query result

Key Value
FileName./usr/share/man/man3/Test::Perl::Critic::Progressive.3pm.xz
FileSize4356
MD57A7F0CA0CE34CE6654612C59C0018B18
SHA-1C9DC4E7221A225A8F727DD52E9E5EFC341364562
SHA-256837C40AEAA3688946CDA28A3EEA76C52225171D456282390C1CD808B38100DBE
SSDEEP96:9ONTcB+9JJNS/rbJBRqfOq8fJsPm9efCAqXVPSGcxldLeTkA:ANg4JNO1uWqSsBDqXBSbnheQA
TLSHT180916E74F86947D316EE17D23964F0523BB38134867A2CB6D475DFEA5E60E013F0429A
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
MD51DF6865D48850DD874A70CD29A6F7E4D
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
PackageRelease10.mga9
PackageVersion0.30.0
SHA-11C6990E8443C36237773CAD15299B02124A48292
SHA-256445FB404E5A835B4D0A9FF59BDEA994C7FBEE3400B8753EC4A5DC079079A291F