Key | Value |
---|---|
FileName | usr/lib/python3.10/site-packages/pako/__pycache__/config_loader.cpython-310.pyc |
FileSize | 2039 |
MD5 | 0E66D984B4F1B6F4ADDEDEA66126741A |
SHA-1 | 6FFC47802CE64D94B19AF8B1AEAE8CD26EFFB8C2 |
SHA-256 | FD565705B2934355122AF3419D1F42B8196A59C916D674D2DF0C902BA92AA636 |
SSDEEP | 48:WbvrZ/cta68jEMTbcOW91pR2h7hOIddG58Wl4dKeasv:6Z/ZTuuRhOCdG58WSdCsv |
TLSH | T1AC41B9CB1305ED66F997F9F8D1190314299777F3778DA0431108B29D7C860E44CF299A |
tar:gname | root |
tar:uname | root |
hashlookup:parent-total | 9 |
hashlookup:trust | 95 |
The searched file hash is included in 9 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileName | http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//armv7//py3-pako-0.3.1-r2.apk |
MD5 | 7AC728B1E36FC141E75F85D5FDD0679D |
SHA-1 | 1575530F02CEA636223835E03E9389826C4405ED |
SHA-256 | 7E1FEC468B69D623959054A0BD037A80052C187DC6EC88224C133322562F527A |
SSDEEP | 384:AxqNMM265g1obnn96Xq0Bs5BloJLAS0d1UC0KhcmyofbpW19Ory:AMp/g1oDn9c5s5EJLAcHmyAbBy |
TLSH | T12F82D0A7DE4E469CC22035F12AD1822F39E62F1DDCB02866DC7242825D2757B8C788F6 |
Key | Value |
---|---|
MD5 | E7D5462DC459B1DCEA4D520F60A4B48B |
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 | python310-pako |
PackageRelease | 4.37 |
PackageVersion | 0.2.3 |
SHA-1 | 62D02438451694C344166054029DD10136769D7D |
SHA-256 | 2E5B866D44B2256FFA16CDC7A0A0B32062E3302076C7BE5940F195F969A2AC13 |
Key | Value |
---|---|
FileName | http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//s390x//py3-pako-0.3.1-r2.apk |
MD5 | ED01792FDA5E01B5C6BAC15C2C151E23 |
SHA-1 | 027718A2C02677D3696E0DCC054A46F69BBD8352 |
SHA-256 | 50B8AEFF58959D4CB05FAFA7948AD9BD3978AD6A31831A000950F4D917CB36DC |
SSDEEP | 384:Yo04qy4M255g1obnn96Xq0Bs5BloJLAS0d1UC0KhcmyofbpW19OrF:Y5deeg1oDn9c5s5EJLAcHmyAbBF |
TLSH | T1B382D0A7EA8B11CC822024F13EF1821B7DE51F1DDCB465A7AC729297593767B88704F2 |
Key | Value |
---|---|
FileName | http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//x86//py3-pako-0.3.1-r2.apk |
MD5 | 42D167D160BA05ABB28E0A7CCDA6A648 |
SHA-1 | 53AEDEC2D3A897EAE93E9AFAEDA3BAFC94C0F891 |
SHA-256 | 24DC234308EE1B22D46F0523F8FCE5774EF4A47552054C753CE2FC17218E6A18 |
SSDEEP | 384:IfJNMM265g1obnn96Xq0Bs5BloJLAS0d1UC0KhcmyofbpW19Ory:Ixp/g1oDn9c5s5EJLAcHmyAbBy |
TLSH | T16482D097EA4B41DC822065F23AE1822F7CE51F1DDCB069679C7241929C2357F88748F7 |
Key | Value |
---|---|
MD5 | 91C95BB23B996DA036CAE8763BCFD7FD |
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 | python310-pako |
PackageRelease | 4.29 |
PackageVersion | 0.2.3 |
SHA-1 | BAD669D65A58F0920AE7F31A094EC6003ED8B13A |
SHA-256 | 6ECB38051592A318AE970B795116940E0F23F2C719DB646F18867BBA51917715 |
Key | Value |
---|---|
MD5 | D08B7E8057498C1DFFF52DE6396BD05E |
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 |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | python310-pako |
PackageRelease | 1.14 |
PackageVersion | 0.2.3 |
SHA-1 | 435D1477572C30E2D3F6F5461609EDC3CAE99A46 |
SHA-256 | 6524B009F9182C827318C465E2806F0D2F89B2204A1D1DE9D444CAD99F309D61 |
Key | Value |
---|---|
FileName | http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//armhf//py3-pako-0.3.1-r2.apk |
MD5 | B4C6DCB884449098C32EC1F1DB9B5FD2 |
SHA-1 | 20C7C18EE92D3A7A2EA8BC0384DA3D818C3DCC2E |
SHA-256 | 342130AB154DAC4829873D14CC27167F1A9176FB388D8EAE14A4ADD9A13CD66C |
SSDEEP | 384:4IbQzGNMM265g1obnn96Xq0Bs5BloJLAS0d1UC0KhcmyofbpW19Ory:4IEzGp/g1oDn9c5s5EJLAcHmyAbBy |
TLSH | T1E982D0A7DD4A529C822028F16DE1812B7DE22F1DDCB074A7AC324196AC2757B8C749F7 |
Key | Value |
---|---|
FileName | http://dl-cdn.alpinelinux.org/alpine/latest-stable//community//x86_64//py3-pako-0.3.1-r2.apk |
MD5 | D341B299F06899A05ED4F20EA189E8B2 |
SHA-1 | EE4330565F456AFC0F02A2081E8B83D5AED8DB29 |
SHA-256 | 3AE26507591AD0EBC994FD629DB0AB85DE06CD16EE50623DC4121279DF434205 |
SSDEEP | 384:i+2mNMM265g1obnn96Xq0Bs5BloJLAS0d1UC0KhcmyofbpW19Ory:i+/p/g1oDn9c5s5EJLAcHmyAbBy |
TLSH | T1D782E097DA4A42DCC22065F139E1822F7DE12B1EDCF02967AC7252969D2352F8C748F6 |
Key | Value |
---|---|
MD5 | 1FAB5D375F872C7479CC08E59D39DC76 |
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 | python310-pako |
PackageRelease | 4.27 |
PackageVersion | 0.2.3 |
SHA-1 | B0E125B06412CA6155B51FEE444764C66DE519A1 |
SHA-256 | C4092C86393E78E7328A61E0BB407948D5B63DFB300691AEA82C494C0A603E3A |