Result for 4F191365FBCD8406EE0AA2D8F0C65A2B77DC48CA

Query result

Key Value
FileName./usr/lib/i386-linux-gnu/libhtmlcxx.so.3.1.0
FileSize75876
MD5D330B864D6893F8A21578A38D6B83699
SHA-14F191365FBCD8406EE0AA2D8F0C65A2B77DC48CA
SHA-256A9E8B20B6A8A707643FD13CD913C3FD9EFC9CA7D7A9DE7A243444966BC1519E0
SSDEEP1536:xKKpYTzDWuDtXf0Yx+vsY0CFdsJXEobzNIC7pS7tlM:lpYTeuD1P8CmAXFbH
TLSHT1F3731726A662C871FCB35EF410C7973A87005932A6E79792F6095F59BC253C05C26BF3
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
FileSize33852
MD5A8A143400C5DA7373B36CAAD1ADD48C5
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.86-1.3
SHA-158ED68A375BDCEAFE2D00E48C93F3C95B36A4F31
SHA-256E0AFB8BA46C338138BB206FF29C44BC68A8A55958E36BE151F2F99D51BC6E9E4