Result for 98463D8C1E91B8E141FA5964E8127899C77FCDE3

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/libhtmlcxx.so.3.1.0
FileSize83572
MD54A66EB87B4C47F118A3283B1C8A3BD35
SHA-198463D8C1E91B8E141FA5964E8127899C77FCDE3
SHA-25652E7D2EB040347462257A0197049E376CE22AEAE95EFA83C7CB6E33401D73241
SSDEEP1536:lGBTmpIA/tXB7NfGcce+ZNP+9kfGRuAnIC7pPDVtt:EBT21VN2rWs8PDVj
TLSHT11F83081AFB42D571ECB36DF8128B87359720993581E783E2BA09575DBC262D04C1ABF3
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
FileSize33760
MD5F90A5BCEA9FEF48950B243CE04460400
PackageDescriptionsimple HTML parser library for C++ htmlcxx is a simple non-validating CSS1 and HTML parser for C++. Although there are several other html parsers available, htmlcxx has some characteristics that make it unique: . * STL like navigation of DOM tree, using excellent tree.hh library from Kasper Peeters * It is possible to reproduce exactly, character by character, the original document from the parse tree * Bundled CSS parser * Optional parsing of attributes * C++ code that looks like C++ (not so true anymore) * Offsets of tags/elements in the original document are stored in the nodes of the DOM tree . The parsing politics of htmlcxx were created trying to mimic Mozilla Firefox (http://www.mozilla.org) behavior. So you should expect parse trees similar to those create by Firefox. However, differently from Firefox, htmlcxx does not insert non-existent stuff in your html. Therefore, serializing the DOM tree gives exactly the same bytes contained in the original HTML document.
PackageMaintainerLudovico Cavedon <cavedon@debian.org>
PackageNamelibhtmlcxx3v5
PackageSectionlibs
PackageVersion0.87-2
SHA-15466B46B419CEEEEFA1C36F9190130362D94790F
SHA-2564B23699C2DB8961D3402378CEE4F4A5EFA413CDE26E5EC8EECB551BC873DA406