Result for 188A2B621F9FC04B9707300993EE37FC430FC35D

Query result

Key Value
FileName./usr/share/maven-fragments/httpcomponents-core.xml
FileSize2120
MD5A20A87DB833A56A97FA0025FBADC84DE
SHA-1188A2B621F9FC04B9707300993EE37FC430FC35D
SHA-2562E72A1FA104FE72E388AFC9AF7366FC4E679A7C84ADF1B9A5C437B212DE2F0AE
SSDEEP48:cNkP6tZN7wNrZNWqtymwNryFqtRmwNrRFCdZN7dy4dywdR4dR2:B65wN5twNRywNGV5dM6
TLSHT18341C4B098FDD4B261B509C1DD72F913BFE4807BE9811289B0EF94450BCACD985B34A6
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