Saravanan666/pypi-org huggingface dataset:
Package: ioc-hunter
ioc-hunterIOC Hunter finds indicators of compromise (IOC). The parse_iocs function can extract IOCs from text.The type_ioc function can determine the IOC type of a string that you pass in.The IOCs that are recognized are:ssdeepsha256sha1md5emailipv4_publicipv4_privateipv6_publicipv6_privatefilenamedomainurlParse IOCsThe parse_iocs function parses IOCs in the list above from text. There is an option
to defang the IOCs that are passed back as well as an option to provide a whitelist regex.
This will also return IOCs labeled asunknownwhen text is found to be suspicious, but doesn't
match any of the IOC types.from ioc_hunter import parse_iocs

text = "Your text goes here"
whitelist = r".*internaldomain\.com.*"
iocs = parse_iocs(text, defang=False, whitelist_regex=whitlist)parse_iocs

Params:
    text – A string to parse.
    defang – If True, defang any IOCs we can (see DEFANGABLE). If False, return IOCs in their fanged state.
    whitelist_regex – Any IOC matching this regex will be ignored
    iocs_to_parse – A list of IOC types to look for (see IOC_TYPES_SEARCH_ORDER for options)
    whitelist_domains – A list or CSV of domains to exclude from results. Excludes domains and URLs that match
    whitelist_ip_cidr_ranges – A list or CSV of CIDR ranges to exclude from results. Excludes IPs and URLs that match
Returns:
    A dictionary with the ioc type as the key and a list of iocs for each value.Type IOCThe type_ioc function takes in text and determines if that text matches any of the IOC types.
If it does not match any, it will returnunkown.from ioc_hunter import type_ioc

suspected_ioc = "mydomain.com"
ioc_type = type_ioc(suspected_ioc)type_ioc

Params:
    ioc – The IOC to classify.
    types_to_find – A list of types you want to look for.
Returns:
    The type of the IOC as a string, (see IOC_TYPES_SEARCH_ORDER for options)
Package: iocingestor
iocingestorAn extendable tool to extract and aggregate IoCs from threat feeds.This tool is a forked version ofInQuest'sThreatIngestorfocuses onMISPintegration.Key differencesBetter MISP integration.Working with the latest version of MISP.Smart event management based onreference_link.MISP warninglistcompatible whitelisting.Usingioc-finderinstead ofiocextractfor IoC extraction.YARA rule extraction is dropped.Installationiocingestor requires Python 3.6+.Install iocingestor from PyPI:pipinstalliocingestorUsageCreate a newconfig.ymlfile, and configure each source and operator module you want to use. (Seeconfig.example.ymlas a reference.)iocingestorconfig.ymlBy default, it will run forever, polling each configured source every 15 minutes.Pluginsiocingestor uses a plugin architecture with "source" (input) and "operator" (output) plugins. The currently supported integrations are:SourcesGitHub repository searchRSS feedsTwitterGeneric web pagesOperatorsCSV filesMISPSQLite database
Package: iocmite
Suricata from to sources CTIthe purpose of the application is to import attributes from different sources of threat Intelligence into suricata datasets to put them under surveillance.Concepts of datasets in SuricataIndicators can be saved in a suricata dataset and create detection rules on this dataset.This concept is detailedhere.Installationgitclonehttps://github.com/sebdraven/iocmite.git
python3-m'venv'venv&&sourcevenv\bin\activate
pipinstall-rrequirements.txt`pythonsetup.pyinstallorpython-m'venv'venv&&sourcevenv\bin\activate
pipinstalliocmite
iocmite--helpDownload the last release of Suricatahereand run:tarxvfzsuricata-6.0.x&&cdsuricata-6.0.x/python&&pythonsetupinstallJson setting and Rule Suricata for MISP source and Sightings{"misp":{"url":"","key":""},"eve_json":"/var/log/suricata/eve.json","metadata":"sightings","tmp_file":"/tmp/last_run","rule":"","datasets":{"sources":{"misp":{"ip-src":{"name":"ips","type":"string"},"ip-dst":{"name":"ips","type":"string"},"hostname":{"name":"dbl","type":"string"},"domain":{"name":"dbl","type":"string"},"user-agent":{"name":"uabl","type":"string"}}}}}Sample signatures are provided in the rules directory. For example, the one matchine on HTTP hostname is:alert http any any -> any any (msg: "domains TA (HTTP)"; http.host; dataset:isset,dbl, type string, state /var/lib/suricata/data/dbl.lst; sid:1100001; rev:1; metadata:sightings http.hostname;)The metadata term in the rule suricata is the same in the setting JSON file. The signatures suppose a standard system wide Suricata installation, you will need to change the path in thestateoption in thedatasetkeyword if ever you don't have a standard installation.Setup the url and key of MISP in the json file.UsagePrinciplesTo synchronize the IOCs in MISP with Suricata datasets, you need to run an import command periodically.
You can use a cron task to do so.To send sightings back to MISP, you need to run a IOCmite instance that will wait for new events
and publish sightings as soon as they came.Example commandsTo import indicators from MISP to suricata with redis to store last run time, run the following command:iocmite--config/path/to/json/file/settings.json--import--redisTo import indicators from MISP to suricata with temp file to store last run time, run the following command:iocmite--config/path/to/json/file/settings.json--import--tmp_fileTo catch alert from redis and send sightings to MISP, run the following command:iocmite--config/path/to/json/file/settings.json--redis--sightingsTo catch alert from eve_json and send sightings to MISP, run the following command:iocmite--config/path/to/json/file/settings.json--eve_json--sightings
Package: io-collection
Collection of tasks for I/O.
Designed to be used both inPrefectworkflows and as modular, useful pieces of code.InstallationThe collection can be installed using:pipinstallio-collectionWe recommend usingPoetryto manage and install dependencies.
To install into your Poetry project, use:poetryaddio-collectionUsagePrefect workflowsAll tasks in this collection are wrapped in a Prefect@taskdecorator, and can be used directly in a Prefect@flow.
Running tasks within aPrefectflow enables you to take advantage of features such as automatically retrying failed tasks, monitoring workflow states, running tasks concurrently, deploying and scheduling flows, and more.fromprefectimportflowfromio_collection.<module_name>import<task_name>@flowdefrun_flow():<task_name>()if__name__=="__main__":run_flow()Seecell-abm-pipelinefor examples of using tasks from different collections to build a pipeline for simulating and analyzing agent-based model data.Individual tasksNot all use cases require a full workflow.
Tasks in this collection can be used without the Prefect@taskdecorator by simply importing directly from the module:fromio_collection.<module_name>.<task_name>import<task_name>defmain():<task_name>()if__name__=="__main__":main()or using the.fn()method:fromio_collection.<module_name>import<task_name>defmain():<task_name>.fn()if__name__=="__main__":main()
Package: io-connect
Project descriptionFaclon I/O Sense Data Access Library
​Where to get ithttps://pypi.org/project/iosense/Installationpip install io_connectpip3 install io_connectFeaturesRetrives following details:User information.Device Details.Device metaData.Time based sensor data of a Device.Published events details.Events data in given timeslot.Event categories.Events data count.DependenciespandasrequestsjsontimedatetimeDocumentationThe official documentation is hosted on​Reach usFor usage questions, please reach out to us atreachus@faclon.com
Package: iocontrol
MicrochipMicrochip I/O Control ApplicationThis application is a graphical application to analyze and manipulate
hardware peripherals using the Microchip Peripheral I/O (MPIO) package.Supported InterfacesADC - Analog-to-Digital ConverterGPIO - General Purpose I/OInput - Input Subsystem (Mouse/Keyboard/Touchscreen)LED - Light Emitting Diode Light SourcesPWM - Pulse Width ModulationInstallationYou can install from PyPi by default with:pip install iocontrolLicenseThe iocontrol application is released under the terms of theGPLv3or later license and its QDarkStyleSheet theme isMIT.
Package: iocp
iocp tries to mimic Go’s io.Copy function (http://golang.org/pkg/io/#Copy)
which copies from everything that is an io.Reader to anything that is an
io.Writer).The Python world of things is not that organized, so iocp.copy will try to do a
best guess about which are the right function to call when reading and writing.For example, checking md5 signature of a file:md5 = hashlib.md5()
with open('/path/to/file') as fo:
    iocp(fo, md5)
print md5.hexdigest()
Package: iocparser
IOC-parserIOC-Parser is a script that will extract the IOCs from a given (text-based) file and output it in .csv-format. Or - as a module - returns a list of instances with an IOC-value and an IOC-type.Installationas a module:pip install iocparseras a stand-alone script:git clone https://github.com/renzejongman/iocparserUsage./iocparser.py -s [source-file] -o [outputfile.csv]Use in a custom scriptfrom iocparser import IOCParser
textObj = IOCParser("text")
results = textObj.parse()Classes.IOC(kind, value)Instances of this very simple class are generated by the IOCParser class.kind="IP", "uri", "md5", "sha1", "sha256", "CVE", "email" or "file"value=The value of the IOCParser-class and returned as a list..IOCParser(text)This class takes a text as input, extracts all the IOCs and returns them as a list of instances of the IOC-class.text=the raw text (as a variable) to be parsed.Other filesextensions:the file extensions needed to detect a filename (and not mistake them for URIs)tlds:the Top Level Domains (TLDs) needed to recognise URI`s (and not mistake them for files)feel free to manipulate those files, but make sure there are no empty lines in either of them, or the script will break.
Package: ioctl-opt
Pythonified linuxasm-generic/ioctl.h.So you can replicate driver’s code computingfcntl.ioctl’soptargument.For example, starting from the following IOCTL declaration (taken frominput.h):#include<sys/ioctl.h>#define EVIOCGNAME(len) _IOC(_IOC_READ, 'E', 0x06, len)/* get device name */you could write the following:fromioctl_optimportIOC,IOC_READEVIOCGNAME=lambdalength:IOC(IOC_READ,ord('E'),0x06,length)The differences are minimal, and all come from python language or coding style:macros/constants to use fromioctl_optfor not start with an underscoredefined macro becomes a callable (here a lambda, could be function)IOC’snrargument has to be an integer, so C’s single-quote char becomes anordcallavoid shadowing built-inlenfunctionThelengthargument is an object (typically serving as an I/O buffer with thefcntl.ioctl()call), the size of which is incorporated in the generated ioctloptvalue.IOC()will
calculate the size of the object.  Supported object types are:anyctypestype or instancememoryviewbytearraystruct.Structarray.arrayYou may want to then write a pythonic function to conveniently access that ioctl:importctypesimportfcntldefgetDeviceName(fd,length=1024):name=(ctypes.c_char*length)()actual_length=fcntl.ioctl(fd,EVIOCGNAME(length),name,True)ifactual_length<0:raiseOSError(-actual_length)ifname[actual_length-1]==b'\x00':actual_length-=1returnname[:actual_length]More advanced example defining hidraw ioctls, requiring structures (for more on how structures are defined, check python’s ctype documentation for your python version):importctypesfromioctl_optimportIOR,IOC,IOC_READ,IOC_WRITE# hid.hHID_MAX_DESCRIPTOR_SIZE=4096# hidraw.hclasshidraw_report_descriptor(ctypes.Structure):_fields_=[('size',ctypes.c_uint),('value',ctypes.c_ubyte*HID_MAX_DESCRIPTOR_SIZE),]classhidraw_devinfo(ctypes.Structure):_fields_=[('bustype',ctypes.c_uint),('vendor',ctypes.c_short),('product',ctypes.c_short),]HIDIOCGRDESCSIZE=IOR(ord('H'),0x01,ctypes.c_int)HIDIOCGRDESC=IOR(ord('H'),0x02,hidraw_report_descriptor)HIDIOCGRAWINFO=IOR(ord('H'),0x03,hidraw_devinfo)HIDIOCGRAWNAME=lambdalength:IOC(IOC_READ,ord('H'),0x04,length)HIDIOCGRAWPHYS=lambdalength:IOC(IOC_READ,ord('H'),0x05,length)HIDIOCSFEATURE=lambdalength:IOC(IOC_WRITE|IOC_READ,ord('H'),0x06,length)HIDIOCGFEATURE=lambdalength:IOC(IOC_WRITE|IOC_READ,ord('H'),0x07,length)
Package: iocursor
io‸cursorAzero-copyfile-like wrapperforPythonbyte buffers,
inspired by Rust'sstd::io::Cursor.🗺️ Overviewiocursor.Cursorlets you wrap an allocated buffer (i.e. a Python object
implementing thebuffer protocol),
and interfacing with it through the API of a file-like object. It shares
some common points withio.BytesIObut with the following main differences:zero-copyVScopy:Cursorwill not copy the data you give it at
initialisation, whileBytesIOwill. This makesCursormore efficient
when you are using it for read-only operations.staticVSgrowable:Cursorwill only use the buffer you give it at
static memory, whileBytesIOwill use its dedicated, growable buffer.🔧 InstallingInstall directly from PyPI, usingpip:$pipinstalliocursorPre-built wheels are available on Linux and OSX for all supported Python3
versions. Otherwise, building from source only requires a working C compiler.🧶 Thread-safetyiocursor.Cursorinstances are not thread-safe. Using severalCursorinstances with the same backend memory only for reading should be fine.
Use a lock when interfacing otherwise.💡 ExamplesUseiocursor.Cursorwhen you havebytesyou need to pass to an interface
that only accepts file-like objects. For instance, pass a PNG image decoded
from base64 to PIL, without copy:importbase64fromiocursorimportCursorfromPILimportImageimgdata=base64.b64decode("iVBORw0KGgoAAAANSUhEU...")img=Image.open(Cursor(imgdata))Useiocursor.Cursorwhen you want to use the file-like API to write
to a buffer of known size. For instance, retrieve a file using thepysmbAPI, which only accepts
file-like objects:fromSMB.SMBConnectionimportSMBConnectSMBConnectionsmb=SMBConnection('guest','','client','server')smb.connect("192.168.0.1")info=smb.getAttributes("Music","The Clash/Rock the Casbah.mp3")cursor=Cursor(bytearray(shared_file.file_size))smb.retrieveFile("Music","The Clash/Rock the Casbah.mp3",cursor)buffer=cursor.getvalue()Useiocursor.Cursorwhen you want to do direct I/O on a type implementing
the buffer protocol. For instance, initialize anumpyarrayby writing bytes
to it:importnumpyarray=numpy.empty(4,dtype="int16")cursor=Cursor(array)cursor.write(b"\x01\x00\x02\x00\x03\x00\x04\x00")print(array)# array([1, 2, 3, 4], dtype=int16)💭 Feedback⚠️ Issue TrackerFound a bug ? Have an enhancement request ? Head over to theGitHub issue
trackerif you need to report
or ask something. If you are filing in on a bug, please include as much
information as you can about the issue, and try to recreate the same bug
in a simple, easily reproducible situation.🏗️ ContributingContributions are more than welcome! SeeCONTRIBUTING.mdfor more details.⚖️ LicenseThis library is provided under theMIT License.
Package: ioc_writer
ioc_writerThe source code in this package is made available under the terms of the
Apache License , Version 2.0. See the “LICENSE “ file for more
information.StatusAuthorWilliam Gibb william.gibb at fireeye dot comPurposeProvide a python library that allows for basic creation and editing of
OpenIOC objects. It supports a basic CRUD (Create, Read, Update, Delete)
for various items:itemCreateReadUpdateDeleteIOC nameYesNoYesYesIOC descriptionYesNoYesYescreated dateYesNoYesN/Alast modified dateYesNoYesN/Apublished dateYesNoYesN/Alink metadataYesNoYesYesIndicatorItem nodesYesNoNotYetYesIndicator nodesYesNoNotYetYesParametersYesNoYesYesItems do not have built in Read operations, since all items can be
accesed with built in ElementTree syntax or the use of XPATH to select
portions of the IOC.No decision has been made about whether or not to support changing of
existing Indicator/IndicatorItem nodes.See the Docs located athttps://pythonhosted.org/ioc_writer/and the
examples directory for examples of working with the library. The user
code should avoid having to call functionality in ioc_writer.ioc_et.RequirementsThe python “lxml” library must be installed. This can be obtained fromhttps://pypi.python.org/pypi/lxmlInstallationSee the file named “INSTALL” for instructions on installing this library
locally.ExamplesExample code lives in the examples folder of the repository.examples/11_to_10_downgrade Script to downgrade OpenIOC 1.1 to
OpenIOC 1.1.examples/openioc_to_yara Scripts that support encapsulating YARA
signatures in OpenIOC 1.1 format.examples/simple_ioc_writer Script that consumes a csv of data to
build an IOC. this csv contains the content, context, et cetera. An
example CSV is provided.Bug reports / questions / feedback / feature requestswilliam.gibb at fireeye dot com
Package: iodata
AboutLicenseIOData is distributed under GPL License version 3 (GPLv3).DependenciesThe following dependencies will be necessary for IOData to build properly,Python >= 2.7, >= 3.5:http://www.python.org/SciPy >= 0.11.0:http://www.scipy.org/NumPy >= 1.9.1:http://www.numpy.org/Nosetests >= 1.1.2:http://readthedocs.org/docs/nose/en/latest/InstallationTo install IOData:`bash python ./setup install--user`TestingTo run tests:`bash nosetests-viodata `
Package: ioddcombase
This is the base package for Siogeen IoddCom.For checking your IO-Link masters working with Siogeen IoddCom, please seeIoddComCheckerorIoddComCheckerGuiFor full package, requests and support go tohttps://siogeen.comCopyright 2017-2023 Siogeen UG(limited liability)Supported PlatformsOSPython 2.7, 3.4-3.5Python 3.6 - 3.11Windows[1]xLinux x86/x64[1]xLinux Arm (Raspberry)[1]3.7-3.11macOS[1]3.8-3.11[1](1,2,3,4)IoddCom for Python 2.7, 3.4 - 3.5 onrequest.Support for other platforms onrequest.Supported operating systems and IO-Link mastersTable of supported IO-Link masters for specific operating systems (OS):Mastersupported OSWindowsLinuxRaspberry PimacOS 64[2]TMG-USB based masters[3]xxxxTMG ethernet based masters[4]xxxxifm ethernet based masters[5]xxxxifm USB based masters[6]xxxxFor Windows, Linux and Raspberry Pi both, 32-bit and 64-bit versions are available.[2]For macOS 13+[3]For example: Baumer, Leuze, Pepperl+Fuchs, SICK AG, Turck[4]For Example: Balluff, Belden, Murrelektronik, Pepperl+Fuchs, Wenglor[5](1,2)All ifm IO-Link masters AL1xxx should be supported. Functionality depends on
master type.
The following functions are missing yet: PD streaming, master data storage read/write,
master commands, PD valid status[6]Experimental ifm USB IO-Link master AL1060 support. Special functions missing
like for[5]Not supported masters:RevolutionPi RevPi mastersPepperl & Fuchs comtrol mastersBaumer USB-C and senscontrol mastersGermbedded mastersTEConcept mastersiO-Fly mastersiq mastersSupport for them or other masters onrequest.
Package: ioddcomchecker
This is the CLI for checking your IO-Link masters working with Siogeen IoddCom.If you want using a GUI seeIoddComCheckerGuiInstallUse pip to install IoddComChecker:>>> pip install IoddComCheckerUsageTo start a scan execute on the console:>>> python -m siogeen.tools.cli.IoddComCheckerCommand line options>>> IoddComChecker [-h] [-a ADDRESS] [--auto] [--version]-h,--helpshow this help message and exit-aADDRESS,--addressADDRESSspecify one or more master addresses (default all)--autoactivate master ports if all are disabled--versionprint versionExample>>> IoddComChecker -a 10.0.0.17 -a 10.0.0.19 --autoFor full package, requests and support go tohttps://siogeen.comCopyright 2017-2024 Siogeen UG(limited liability)Supported PlatformsOSPython 2.7, 3.4-3.6Python 3.7 - 3.12Windows[1]xLinux x86/x64[1]xLinux Arm (Raspberry)[1]xmacOS[1]3.8-3.12[1](1,2,3,4)IoddCom for Python 2.7, 3.4 - 3.6 onrequest.Support for other platforms onrequest.Supported operating systems and IO-Link mastersTable of supported IO-Link masters for specific operating systems (OS):Mastersupported OSWindowsLinuxRaspberry PimacOS 64[2]TMG-USB based masters[3]xxxxTMG ethernet based masters[4]xxxxifm ethernet based masters[5]xxxxifm USB based masters[6]xxxxFor Windows, Linux and Raspberry Pi both, 32-bit and 64-bit versions are available.[2]For macOS 12.3+[3]For example: Baumer, Leuze, Pepperl+Fuchs, SICK AG, Turck[4]For Example: Balluff, Belden, Murrelektronik, Pepperl+Fuchs, Wenglor[5]All ifm IO-Link masters AL1xxx should be supported. Functionality depends on
master type. The following functions are missing yet: PD valid status[6]ifm USB IO-Link master AL1060: Special functions missing
HW PD streaming (yet by SW), PD valid statusNot supported masters:REST API based masters:Support from V1.7 on(Sick SIG200/SIG350, Belden Lion-X, MurrElectronik Impact67 Pro/MVK Pro, Balluff)RevolutionPi RevPi mastersPepperl & Fuchs comtrol mastersBaumer USB-C and senscontrol mastersGermbedded mastersTEConcept mastersiO-Fly mastersiq mastersSupport for them or other masters onrequest.
Package: ioddcomcheckergui
This is the GUI for checking your IO-Link masters working with Siogeen IoddCom.For using CLI only useIoddComCheckerInstallUse pip to install IoddComCheckerGui:>>> pip install IoddComCheckerGuiUsageTo start the Gui execute:>>> python -m siogeen.tools.gui.IoddComCheckerFor full package, requests and support go tohttps://siogeen.comCopyright 2017-2024 Siogeen UG(limited liability)Supported PlatformsOSPython 2.7, 3.4-3.6Python 3.7 - 3.12Windows[1]xLinux x86/x64[1]xLinux Arm (Raspberry)[1]xmacOS[1]3.8-3.12[1](1,2,3,4)IoddCom for Python 2.7, 3.4 - 3.6 onrequest.Support for other platforms onrequest.Supported operating systems and IO-Link mastersTable of supported IO-Link masters for specific operating systems (OS):Mastersupported OSWindowsLinuxRaspberry PimacOS 64[2]TMG-USB based masters[3]xxxxTMG ethernet based masters[4]xxxxifm ethernet based masters[5]xxxxifm USB based masters[6]xxxxFor Windows, Linux and Raspberry Pi both, 32-bit and 64-bit versions are available.[2]For macOS 12.3+[3]For example: Baumer, Leuze, Pepperl+Fuchs, SICK AG, Turck[4]For Example: Balluff, Belden, Murrelektronik, Pepperl+Fuchs, Wenglor[5]All ifm IO-Link masters AL1xxx should be supported. Functionality depends on
master type. The following functions are missing yet: PD valid status[6]ifm USB IO-Link master AL1060: Special functions missing
HW PD streaming (yet by SW), PD valid statusNot supported masters:REST API based masters:Support from V1.7 on(Sick SIG200/SIG350, Belden Lion-X, MurrElectronik Impact67 Pro/MVK Pro, Balluff)RevolutionPi RevPi mastersPepperl & Fuchs comtrol mastersBaumer USB-C and senscontrol mastersGermbedded mastersTEConcept mastersiO-Fly mastersiq mastersSupport for them or other masters onrequest.
Package: iode
IODE - Management of isolated VSCODE environmentsIODE is a command-line tool that makes it easy to maintain and manage isolated vscode environments written in Python.InstallationOption 1 : Install from pypipip install iode --userOption 2 : Install from sorucegit clone https://github.com/jugangdae/iode
cd iode
pyhton -m build
pip install iode-0.0.1-py3-none-any.whlCommandscreate: Create a new IODE environment.iode create [iode_env]
iode c [iode_env]list: Show iode env listiode list
iode lrun: Executes VSCODE using an IODE environmentiode run [iode_env] [work_path]
iode r [iode_env] [work_path]Delete: Delete an IODE environment.iode delete [iode_env]
iode d [iode_env]helpandversioniode -h, --help
iode -v, --versionConfig (~/.iodeconfig)[setting]
iode_run = [code or code-insider]
iode_dir = [path of iode environments directory]