Result for 6736138F4AB89CF88A9B6D9DE0AC5F2A96F26B5F

Query result

Key Value
FileName./usr/share/java/munge-maven-plugin/munge-maven-plugin.jar
FileSize15233
MD568DA7B6E1A6287059B16CF72F707F6B8
SHA-16736138F4AB89CF88A9B6D9DE0AC5F2A96F26B5F
SHA-256254F57067AD65585300DE584DE61970CF30C9539C930B0AB5E8E699B0C7784B4
SSDEEP192:Bpo3LRSPLf4v4A1GHxqmsrsT7uVTEQ7rFfkSQSKOdfM62ikmO0Sne:43LRSD4wAUxqhrsPiF1MSQdDmTSe
TLSHT1F8628E3ADDD76D3CD73EC6B0071560C712CD529E63EBEB6326D43AA50EB18158B0B264
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
MD51AEFE58E1638390FC4390E093EF47DCB
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.
PackageNamemunge-maven-plugin
PackageRelease7.298
PackageVersion1.0
SHA-12CFCF5EAAE87689926F7559E553260CA41857620
SHA-2562638D1D8484685AF30CC4CB9608B829376F891AE2714FAECD678ACF31581561C