Result for 07731CB16176CD7A2A563C0F023CDD61D88CF621

Query result

Key Value
FileName./usr/share/maven-poms/JPP.logback-logback-core.pom
FileSize5529
MD5FAD820D36F93F2954B1B596576923D58
SHA-107731CB16176CD7A2A563C0F023CDD61D88CF621
SHA-2563E5FEBF2E1251BA17F7F5225656AFC13772FE90ADCA856E476E5910FACA16B31
SSDEEP96:UHV72eB1mw+Jvu8B8IF4nrrFVLqF5l8pBrEq1iEd/ra:872eB1XOjF4nrrFVLqfl8pBrv1iEd/2
TLSHT1E4B1E075C8CE743062F748C6CE71C269FF7AD2A790068004F59CA3876F78DCA8567956
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