Result for 42380E8F3133703157C68DBD01763540620A0156

Query result

Key Value
FileName./usr/share/maven-repo/org/apache/logging/log4j/log4j-to-slf4j/debian/log4j-to-slf4j-debian.pom
FileSize2123
MD5120CAA680B3C02620E5493F261C87B4A
SHA-142380E8F3133703157C68DBD01763540620A0156
SHA-25653565E53148A1B62B77BBBCFBC0E00CC0DCC4104D12781695033F742F78C6C86
SSDEEP48:cNxKAhNIAh0ehzH31cyp82HxHXQqbV785XIrpKIm2hsOvFJ1qU:2QAPIAPzHFciHxg8Q76vJr
TLSHT1E14165E9F88DDA3153DC4ECA9F3A805AA73BA1BC6059C3C4F049C04967685AE05F6276
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize2079820
MD517AF905049F78235CCE0BEE30D801B38
PackageDescriptionApache Log4j - Logging Framework for Java Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x: . API Separation: The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. . Improved Performance: Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios Asynchronous Loggers have 10 times higher throughput and orders of magnitude lower latency than Log4j 1.x. . Support for multiple APIs: While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and Commons Logging APIs. . Automatic Reloading of Configurations: Log4j 2 can automatically reload its configuration upon modification. It will do so without losing log events while reconfiguration is taking place. . Advanced Filtering: Log4j 2 supports filtering based on context data, markers, regular expressions, and other components in the Log event. Filtering can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. . Plugin Architecture: Log4j uses the plugin pattern to configure components. As such, no code is needed to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically recognizes plugins and uses them when a configuration references them. . Property Support: Properties can be referenced in a configuration, Log4j will directly replace them, or Log4j will pass them to an underlying component that will dynamically resolve them. Properties come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event.
PackageMaintainerDebian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
PackageNameliblog4j2-java
PackageSectionjava
PackageVersion2.17.0-1~deb10u1
SHA-1567114F46336F639C26569F7757ECD2DD1DDCE39
SHA-25603EA31D232051FD1CC9D73D1A21BF01C261F3D03F8364D57BC2F36DCE48DF46C
Key Value
FileSize2076840
MD5B3CACB0BF9A627986621F96F0094B078
PackageDescriptionApache Log4j - Logging Framework for Java Apache Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x: . API Separation: The API for Log4j is separate from the implementation making it clear for application developers which classes and methods they can use while ensuring forward compatibility. . Improved Performance: Log4j 2 contains next-generation Asynchronous Loggers based on the LMAX Disruptor library. In multi-threaded scenarios Asynchronous Loggers have 10 times higher throughput and orders of magnitude lower latency than Log4j 1.x. . Support for multiple APIs: While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and Commons Logging APIs. . Automatic Reloading of Configurations: Log4j 2 can automatically reload its configuration upon modification. It will do so without losing log events while reconfiguration is taking place. . Advanced Filtering: Log4j 2 supports filtering based on context data, markers, regular expressions, and other components in the Log event. Filtering can be specified to apply to all events before being passed to Loggers or as they pass through Appenders. . Plugin Architecture: Log4j uses the plugin pattern to configure components. As such, no code is needed to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically recognizes plugins and uses them when a configuration references them. . Property Support: Properties can be referenced in a configuration, Log4j will directly replace them, or Log4j will pass them to an underlying component that will dynamically resolve them. Properties come from values defined in the configuration file, system properties, environment variables, the ThreadContext Map, and data present in the event.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNameliblog4j2-java
PackageSectionjava
PackageVersion2.17.0-0.20.04.1
SHA-15D774DB3557955E9394288421885D1FFD771A707
SHA-256F51F23ACA7907BEE8328EE38FC08BBD51D0C79B87FE7F5A6F1C7F693742A8820