Query result

Key	Value
FileName	./usr/lib64/python3.6/site-packages/snimpy/__pycache__/snmp.cpython-36.pyc
FileSize	12939
MD5	C7CB71A8D684E69B5FEE1A91188056F8
SHA-1	234B7AF9C09D7E4C1A88B35BAB2CF518549BF718
SHA-256	4D1B2590B87F9DC0EF2213A3959E93C7AE7DF88D8F7A7F5E3FF945349F53183A
SSDEEP	384:s1iiqqCqqHqq1qqiyyPTeenp0l3FHEzw8PEQqzqwDWPIqtBRWq8YN1Bt9b4dbqv5:sQiqqCqqHqq1qqizTRWFkrZqzqwiPIqj
TLSH	T1DA4208D466462377FA29F2BD825522B09B38C273335E4186702CC97F2F878607CB5E86
hashlookup:parent-total	1
hashlookup:trust	55

Network graph view

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	1E9E894E56C08BAB9C02479E40A03D2C
PackageArch	x86_64
PackageDescription	Snimpy is a Python-based tool providing a simple interface to build SNMP query. You can either use Snimpy interactively through its console (derived from Python own console or from IPython_ if available) or write Snimpy scripts which are just Python scripts with some global variables available. Snimpy is aimed at being the more Pythonic possible. You should forget that you are doing SNMP requests. Snimpy will rely on MIB to hide SNMP details. Here are some "features": * MIB parser based on libsmi (through CFFI) * SNMP requests are handled by PySNMP (SNMPv1, SNMPv2 and SNMPv3 support) * scalars are just attributes of your session object * columns are like a Python dictionary and made available as an attribute * getting an attribute is like issuing a GET method * setting an attribute is like issuing a SET method * iterating over a table is like using GETNEXT * when something goes wrong, you get an exception
PackageMaintainer	https://bugs.opensuse.org
PackageName	python3-snimpy
PackageRelease	lp152.1.3
PackageVersion	0.8.13
SHA-1	98864D05142CB0A87580571BDC62B5C17CFD4D03
SHA-256	6C9A12ADE45C1B48DA7CF9EA4D5A439768CBB675BCF74BD30AAEBCE2E47734BE