Result for CA87ACB779DEECF2596F36B9858ACA25EE716A90

Query result

Key Value
FileName./usr/share/maven-effective-poms/JPP.httpcomponents-httpcore-nio.pom
FileSize585
MD5AA6D48E7B3761E3EF582D5315D9AB34A
SHA-1CA87ACB779DEECF2596F36B9858ACA25EE716A90
SHA-2561970C8844C61D62DCCB7182038F0DA092D821A961B09CC95E5FF9DAE878A87B0
SSDEEP12:TMrG9tEeQE+8SKkEey8iD2aSAyyhy9J2MLF0KOOeohSFwKJ2MLyeOelZZKBAPtL:KkgKay8y2RAHCJNROE4tye/nKBo
TLSHT156F028E4C1FCD0B1A1964EC0D9E619139BB1807AE0C812C5F0CE9886534C8CF407345B
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
CRC32FEE36103
FileNamehttpcomponents-core-4.2.4-6.el7.noarch.rpm
FileSize476764
MD58BAF46327997B607531EBC38B91A45B9
OpSystemCode362
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.
PackageMaintainerCentOS BuildSystem <http://bugs.centos.org>
PackageNamehttpcomponents-core
PackageRelease6.el7
PackageVersion4.2.4
ProductCode202232
SHA-1E56DB1417AE92102D5F02A3780EC11FD8CB408B1
SHA-256A33F4D3B295171C9C4E31903A3627E48650FBD63DA4865D2E16528C5CA9D1546
SpecialCode
dbnsrl_modern_rds
insert-timestamp1647061811.9994073
sourceNSRL