| Key | Value |
|---|---|
| FileName | ./usr/bin/pako-3.8 |
| FileSize | 369 |
| MD5 | 6C2A47904E5247C64B05970538E10648 |
| SHA-1 | 0400C620A7DF9A08B8BC7E1E29B542B4744F6FED |
| SHA-256 | 3B0301C30C21DB8015FE602767B9AB0F69E763171A9F4BC68F49FD6B0DF64134 |
| SSDEEP | 6:HWaHwedaxtKX+HXXnXFD/J/VAoLGtrVV1CFAjaj+iQDF7M1tQDaSbrVVySHSdw:HRwKuHXXqoi9VrCF2aGNM1m2SfVb0w |
| TLSH | T172E0C0128831CE6045B2C18B28F06064227F0D637620E002F3E45A7EBBC03C93C30F26 |
| 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 | 63A8C288F97F53253E399AC64A747BCF |
| PackageArch | noarch |
| PackageDescription | Often, scripts need to install system dependencies using the native package manager of the user's OS. Typically, this is solved by having some bash script that runs apt-get, assuming the user is on Ubuntu. Smarter scripts use hand crafted code to detect the user's platform and aggregate a set of dependencies on a few of the more popular platforms. Our approach is different: * Parse package format (devel/debug/normal library or executable) * Look up package managers that exist in PATH * Format parsed package with common package convention of package manager More on https://github.com/MycroftAI/pako |
| PackageName | python38-pako |
| PackageRelease | 1.6 |
| PackageVersion | 0.2.3 |
| SHA-1 | 842FB9DF5861E59BEADB1B9FF79138B57BDDA115 |
| SHA-256 | 39C421C6D948565AC5E0E16FCD890FB3155387DD0D175193B49C88241F72AEAF |