Result for 8E2E2BEDE3693803EAC58059588C0D433F65EE8F

Query result

Key Value
FileName./usr/share/maven-metadata/httpcomponents-core.xml
FileSize2689
MD531B3E27F9D598C4F9880B22F6DEAC199
SHA-18E2E2BEDE3693803EAC58059588C0D433F65EE8F
SHA-2569038F73CA09FEB8BA40C83C09F70DDA55566F178CC3CFD18F054A2ECAB73E88C
SSDEEP48:cmAUtZNdFKYaty2RCatydkCatR2IOCSINysh7hatRdjKCSINysh7hW:LAUPQYa7RCaekCaqIOCSIbXaxjKCSIbG
TLSHT1365106F4EAFD507172940AC0DE32A993DFD4D0B7E8915289B0CE55948FCACCA85B3156
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
MD58E022A42A9EBFA630FE9CEE06074EC95
PackageArchnoarch
PackageDescriptionHttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease1.module_f28+4409+43f8f627
PackageVersion4.4.11
SHA-18311940DAA3355A7A629D63997F53BAC94733A77
SHA-256B852E73CB8344B8956D62823E0EE2A2B3D01ECE75058F9B829B640C1F231438A
Key Value
MD58448844877E55454CB0D565CF066F125
PackageArchnoarch
PackageDescriptionHttpCore is a set of low level HTTP transport components that can be used to build custom client and server side HTTP services with a minimal footprint. HttpCore supports two I/O models: blocking I/O model based on the classic Java I/O and non-blocking, event driven I/O model based on Java NIO. The blocking I/O model may be more appropriate for data intensive, low latency scenarios, whereas the non-blocking model may be more appropriate for high latency scenarios where raw data throughput is less important than the ability to handle thousands of simultaneous HTTP connections in a resource efficient manner.
PackageMaintainerFedora Project
PackageNamehttpcomponents-core
PackageRelease1.module_f28+4409+43f8f627
PackageVersion4.4.11
SHA-13324424E045A841626772C9E1A756FCF2B3E0038
SHA-25654126A46046CE827DCBF57429DD76F202ABFFFBF3BC7CB8C04011EF40D1CC41D