Result for B17E8671AA65BBB687470EFA53238D6C2E26B651

Query result

Key Value
FileName./usr/lib/arm-linux-gnueabi/libhtmlcxx.so.3.1.0
FileSize63640
MD5C9FE1F2599DD446C76D13CF98A131643
SHA-1B17E8671AA65BBB687470EFA53238D6C2E26B651
SHA-256A3DF73BE0C8638B4FEC185627CBF13E5F6E623ED5DB61073024460472B95FD7E
SSDEEP1536:UD24TeC0RAP0gxyz8cfosGl906zC7pLN:M24TTxyz7ffG2
TLSHT1FC531783C9A79F66C8C07A3671DF532A73035EBCDAFF6345891480219F9A49A1C36F90
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
FileSize27006
MD5E8933D94BCABDB3E538913B8AC2F9D13
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.1+b1
SHA-104D1BF2F7509DBA21283DC7EB283F5B47F13A754
SHA-25621C80B03E820879E8C4B6966E566C477651C0052D79097562CCBF1B061F14F56