Result for E49188D11F370D324F24076804B84E7DF194D213

Query result

Key Value
FileName./usr/share/java/munge-maven-plugin/munge-maven-plugin.jar
FileSize15233
MD525220342C7EF059C011435DCDBCB4104
SHA-1E49188D11F370D324F24076804B84E7DF194D213
SHA-256CAA5A32C961A8A32C8811968C9CCBFA0368BE7E868163A0D495FABB893EACBE6
SSDEEP192:7po3aBJdf22ikUMTEQ7tSPLf4v4A1GHxqmsrsT7u3FfkSQSKsOybrk:a3ADU8FBSD4wAUxqhrsP6MSQE90
TLSHT1A4628E3A55DB6D3CE63F8AF0071160C712CD135E62EADB7517943AB50EF28574B0B2A8
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
MD5F616BE802601DCC27BC59818C0ED9C31
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.456
PackageVersion1.0
SHA-1317D77C01B5412A415586E471B9ADAE3FB42CB00
SHA-256C7AAFF14009D194E964A5798F36B2A0EA83B14CDEC5D4929E63158C65F2D42F4