Result for 08DEDF20F9A547916E4C48EF2DCA07AFA0E2F210

Query result

Key Value
FileName./usr/share/maven-poms/JPP.logback-logback-parent.pom
FileSize13638
MD513581036A9B8A4682A8D3AAD12459C80
SHA-108DEDF20F9A547916E4C48EF2DCA07AFA0E2F210
SHA-2568F4AB857356E104B10B0A0D9801758531627D60580940EE3325B3BB61705F1BA
SSDEEP384:tJvtjYEuCAuCceAeDo7Alf8fIxQyRzpQCRb60RE33dRpGoGy1vwqLgjDr9SP3qIc:tJvtjYEuCAuCceAeDo7Alf8fIxQyRzpZ
TLSHT143529CB5D8CDB07261B685C1DA72C6A1FF6E42ABD0075048F05CA3076FF8CAE85B7916
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
MD5B54F7D106A56FEC2AC193FA3B12519E6
PackageArchnoarch
PackageDescriptionLogback is intended as a successor to the popular log4j project. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core.
PackageMaintainerFedora Project
PackageNamelogback
PackageRelease1.fc16
PackageVersion1.0.1
SHA-1E40E53D84635A34C57355FCB1BDD5E7058F282ED
SHA-25611B113D4F4826E4982326A2385D8E4E6E6BE5A653E5DDB69EDAD557FCFA5A7EB