Result for 30688C1A90AFBF25470270D3F8176191C9FE183A

Query result

Key	Value
CRC32	17F24ABD
FileName	./usr/share/doc/perl-Test-Perl-Critic-Progressive/README
FileSize	8890
MD5	5E4CCDC09FDA38096775BA5DD7F1BD70
OpSystemCode	{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode	{'ApplicationType': 'Software', 'Language': 'English', 'MfgCode': '1533', 'OpSystemCode': '28', 'ProductCode': '17352', 'ProductName': 'CPAN Comprehensive Perl Archive Network Complete Mirror 2016-01-20', 'ProductVersion': '2016-01-20'}
SHA-1	30688C1A90AFBF25470270D3F8176191C9FE183A
SHA-256	8F5E598C41ED45E9A5E6C242C40EF1E13A951B8DAA032A552E46F6F57DC9D58A
SSDEEP	192:oRqF+MvKCiPgY1wZmefxZSfxn3WPQ2xE8XLNZjuhDCEVmfx:oRu+MChPzgEAjUVmZ
SpecialCode
TLSH	T11902321E6A8A03B90583637A6B6F52D2E330C1BF1153521974AE915D2F8BF29C2F74E1
db	nsrl_modern_rds
insert-timestamp	1646996322.707084
source	NSRL
hashlookup:parent-total	37
hashlookup:trust	100

Network graph view

Parents (Total: 37)

The searched file hash is included in 37 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	19C882FADFFB5EB14BE996DDEF7BDA33
PackageArch	noarch
PackageDescription	Applying 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 Perl::Critic engine to prevent further deterioration of your code and gradually steer it towards conforming with your chosen coding standards.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	5.fc16
PackageVersion	0.03
SHA-1	0067A268268B1D0896BE5FB957498454CA6E77A2
SHA-256	0D807F9DBC663D0E739DB4CCCC1A20C04B369395569406EF363DE68BB6CB8E93

Key	Value
MD5	79A07A13208CF98C71D778E26D986577
PackageArch	noarch
PackageDescription	Applying 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 Perl::Critic engine to prevent further deterioration of your code and gradually steer it towards conforming with your chosen coding standards.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	11.fc20
PackageVersion	0.03
SHA-1	00BB1C15542C4574993AC869483F88EFE66D190D
SHA-256	2B15E498BD9C8981608C66FE9D32799CA5428485BCF7955397D84AC67E085049

Key	Value
MD5	34BAEAA1E3A62A79701DD35971BF6D1D
PackageArch	noarch
PackageDescription	Applying 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 Perl::Critic engine to prevent further deterioration of your code and gradually steer it towards conforming with your chosen coding standards.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	12.fc21
PackageVersion	0.03
SHA-1	09C3F61F27420D4B4E613B164E49CC40BB74B672
SHA-256	B253B3BA7F5C87953B0C36F1652BEAA8773322E1D10D84CA020229E4DEBAD688

Key	Value
MD5	CC296FF667807FCB037C93B9255BEDC9
PackageArch	noarch
PackageDescription	Applying 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 Perl::Critic engine to prevent further deterioration of your code and gradually steer it towards conforming with your chosen coding standards.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	5.fc16
PackageVersion	0.03
SHA-1	0D7345CE192DEC8D6717A2487398FCF9F58385BC
SHA-256	46D3BACD0293E32AED95A5A28781B6151F78393DBD94C9C584DB8905D8129E43

Key	Value
MD5	8C28FEECC62F2E4DEC173006741B1177
PackageArch	noarch
PackageDescription	Applying 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.
PackageMaintainer	umeabot <umeabot>
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	9.mga8
PackageVersion	0.30.0
SHA-1	0EC3FB6C142DDD5D498230244FAA928970806833
SHA-256	8F5B0259101B24D13209C24325A5213A7FF85660A500B858BB72D6BA07DAC873

Key	Value
MD5	1DF6865D48850DD874A70CD29A6F7E4D
PackageArch	noarch
PackageDescription	Applying 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.
PackageMaintainer	umeabot <umeabot>
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	10.mga9
PackageVersion	0.30.0
SHA-1	1C6990E8443C36237773CAD15299B02124A48292
SHA-256	445FB404E5A835B4D0A9FF59BDEA994C7FBEE3400B8753EC4A5DC079079A291F

Key	Value
MD5	2DB7AEB8A772672601F4DA5B8ACE1098
PackageArch	noarch
PackageDescription	Applying 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.
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	lp151.4.1
PackageVersion	0.03
SHA-1	1EC0E5897F2149E3F28001B09C7BE89DC22DF7AD
SHA-256	04CF78B21B7B1E724496D15992D64F3B8E00F41AF29D5B963819FA484957A45A

Key	Value
MD5	53CB2003318BA27203ABCE4EF732D849
PackageArch	noarch
PackageDescription	Applying 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 Perl::Critic engine to prevent further deterioration of your code and gradually steer it towards conforming with your chosen coding standards.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	8.fc18
PackageVersion	0.03
SHA-1	2224860921552B495D35FF0CFDC9D00AB425A143
SHA-256	9CD019D2D1BA83EBE4961EEE4D5452A345F319552CAA17E111911855519ADAE5

Key	Value
MD5	8173D68161CFB436B007AF396AD8A8B7
PackageArch	noarch
PackageDescription	Applying 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 Perl::Critic engine to prevent further deterioration of your code and gradually steer it towards conforming with your chosen coding standards.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	13.fc22
PackageVersion	0.03
SHA-1	24AAF8C6F265F392F80CC333B0088760C7787C18
SHA-256	A752DB389D4386B57D4218BF6A2ECB93E9D9ECD4AB810252F2C047991BB9A0A2

Key	Value
MD5	47A7CF01E02F7D5E746C27357358E5DB
PackageArch	noarch
PackageDescription	Applying 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 Perl::Critic engine to prevent further deterioration of your code and gradually steer it towards conforming with your chosen coding standards.
PackageMaintainer	Fedora Project
PackageName	perl-Test-Perl-Critic-Progressive
PackageRelease	12.fc21
PackageVersion	0.03
SHA-1	3CB4B7CDCB9E247B0B9F8A9F95171C7310A06056
SHA-256	93423A58358262B8D47E49B93216CBB27B1FFA72B3DC808306403C88D910D54E