Result for F32C25B4E8307F249ABE4288FE2D9E8DB51278FE

Query result

Key Value
FileName./usr/share/java/munge-maven-plugin/munge-maven-plugin.jar
FileSize15243
MD524AC484EEF5D72046B2E4139BAAD4199
SHA-1F32C25B4E8307F249ABE4288FE2D9E8DB51278FE
SHA-256FA547B46817FFAF85B8E33C842245E496558C0E6DC8EE9A2F43398F9295E811B
SSDEEP384:53WDYmtFRVDbBFsSD4wAUxqhrsPvMSQE4JH:5GTtFRRIS0BUxorsPlC
TLSHT1F1627E7A51DBAE3DDB3E87B0075AB0C312CD02BE67D6DB561B943EB51E714014E0B268
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
MD592B6AA0E8D51FF18F22BF1CCAC5DAF2C
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.545
PackageVersion1.0
SHA-11FE9FBD84E3A1320148578AD5570FBCCA4ECEE22
SHA-256CA4443F0D21F41F0C495A0314E1DB16DFCDC3D877C8F275EA98DFCBC10DC1ED2