Result for 961A8414FA9E6DD859A1150F7707FCCD67B6F16B

Query result

Key Value
FileName./usr/share/java/munge-maven-plugin/munge-maven-plugin.jar
FileSize15174
MD553EAB5E55ABD3927478E01CE6798F785
SHA-1961A8414FA9E6DD859A1150F7707FCCD67B6F16B
SHA-256F7779CF79695DBEF17733CDF287A52B6A1D679A18B7E38ACB560550E2D97FD4C
SSDEEP384:zf4oFZWT1r11mrxG2T9jd0Nlqe+ZxRTIAf032:BFU1rH8zd0wtIAG2
TLSHT116628EB0808A2EB9FB3F4BF843538497019E00DDB3CE476652F6BA962D314594F67664
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
MD54F4A0B6466121AEEDBE78D05D1CA056D
PackageArchnoarch
PackageDescriptionMunge is a purposely-simple Java preprocessor. It only supports conditional inclusion of source based on defined strings of the form "if[tag]", "if_not[tag]", "else[tag]", and "end[tag]". Unlike traditional preprocessors, comments, and formatting are all preserved for the included lines. This is on purpose, as the output of Munge will be distributed as human-readable source code. To avoid creating a separate Java dialect, the conditional tags are contained in Java comments. This allows one build to compile the source files without pre-processing, to facilitate faster incremental development. Other builds from the same source have their code contained within that comment. The format of the tags is a little verbose, so that the tags won't accidentally be used by other comment readers such as javadoc. Munge tags must be in C-style comments; C++-style comments may be used to comment code within a comment. Like any preprocessor, developers must be careful not to abuse its capabilities so that their code becomes unreadable. Please use it as little as possible.
PackageMaintainerFedora Project
PackageNamemunge-maven-plugin
PackageRelease16.fc32
PackageVersion1.0
SHA-1041DB895802360C4FA0F996D1935D4D543F5490C
SHA-256954FC533C4C701F6F5E4709CF26AB2337C89CAB4456606B526A8402A0FD74434