Key | Value |
---|---|
FileName | ./usr/lib64/ghc-8.4.4/xdg-basedir-0.2.2-I9cOiu1LJdUGTkJ3k3nkuZ/libHSxdg-basedir-0.2.2-I9cOiu1LJdUGTkJ3k3nkuZ-ghc8.4.4.so |
FileSize | 35720 |
MD5 | CDCD4C9AED9166B9750241CE6E24042E |
SHA-1 | A03E3AA5B8905F4754ABA6055F7363D3D5C724D7 |
SHA-256 | A3CAC2848BA3293E01CD19E68B3143286A6EEBC7D6DE4E897F4915245CD409E2 |
SSDEEP | 384:BNTXJqJB2+3OHAweveWCqFXSql4OXlss6IXtd:BVXJGZ3OHAweveWCJ4sNm |
TLSH | T1A2F233B323B44BADCAFD4730D60ABEF48670974F1A97E23F1764162CDC1212661DA5E2 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
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 |
---|---|
MD5 | 9F10B975C0FE8D277A0AC0CBAC32C135 |
PackageArch | x86_64 |
PackageDescription | On Unix platforms, this should be a very straightforward implementation of the XDG Base Directory spec. On Windows, it will attempt to do the right thing with regards to choosing appropriate directories. |
PackageName | ghc-xdg-basedir |
PackageRelease | lp150.3.2 |
PackageVersion | 0.2.2 |
SHA-1 | 0412E3E84D954ED094265F5C8BE16AF109957A15 |
SHA-256 | 1713EB567E76209E5845FDCFEDC9B784B0CBADD53506574832F9AEF7B45EDB0F |