Result for B0A11CC55787EAB41B131FFAB49EA6CB59AF4F1C

Query result

Key Value
FileName./usr/share/maven-effective-poms/JPP.httpcomponents-httpcore-nio.pom
FileSize42060
MD501E8DF2027D8F98B25C5A76618567818
SHA-1B0A11CC55787EAB41B131FFAB49EA6CB59AF4F1C
SHA-25604CF3442F8121384A0512E030DA47A86517F629E0A16AD13F0F8141010EB1CB4
SSDEEP768:OdGbFGL87YizU9ursxXz+oD9KAmUrXOJ+DjJnQvZFc9xvZFc9XvZFc9C/JVs9h2+:Ocb/zU9ursxXz+oD9KAmJ+DWvZFc9xvt
TLSHT12013EFF19CFC59B2215609C65B2169C2FFF9C2EBD8858048F1DD5B056F8DDCE82A3A12
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
MD5ED4FE72CDEAC93FB84844F3ED8BD8F87
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
PackageRelease5.fc20
PackageVersion4.2.4
SHA-1E928D9263910169485F92829E8F1BF78322E3211
SHA-2569A0C6A9657F7C88B5737D96D100562B2217DF442F9E36E5F2FA07DDED8E02C61
Key Value
MD5C178CDCFC889F9859297B1F77C8B2CEE
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
PackageRelease5.fc20
PackageVersion4.2.4
SHA-1CA3CE3A386D272818B894F696580831ACFFE67A6
SHA-256A562688ECE9B6D355711C7F312BE05AA141D33106BFD86CB14C4616240C6F94A