Result for B86E9B7AD7977BCD2B2BDE5A1E97D27CF5BFF02C

Query result

Key Value
FileName./usr/share/maven-poms/httpcomponents/httpcore-nio.pom
FileSize5551
MD5A4C5EB7EA44A8BE68FBC9C74C02C7F7F
SHA-1B86E9B7AD7977BCD2B2BDE5A1E97D27CF5BFF02C
SHA-256733A682187199152DFEEF3A24B38FF1BAC1E6AA16F134CA15DF662DCEF47A18D
SSDEEP96:4QWR9VHFgRSH2gb9l4kMX5vQMj2B8oosvq8w4PFeAt4lc9s:e9VHmgb9l4kMX5v32NosC2PFeAtWc9s
TLSHT17FB132B1DCFD54B2239109CAAF229482FFB6C1B7E0898148F48C87446F5DFCA81B3956
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