PyFunnels
The goal of PyFunnels is to create a collaborative code library which makes integrating data into automated workflows easier. The library acts as a centralized location where everyone can contribute and use code.
PyFunnels consists of multiple classes structured modularly so that additional tools and data points can be easily added and work independently of one another. The classes within the library can be thought of as a catalog of tools and methods to retrieve data. Not all data point methods are required for each tool, meaning a new tool can be added with only a single method. Ideally, all data points would be supported for each tool but this structure allows the functionality to grow organically and makes it easy to contribute code to the project.
The library reduces the time it takes information security professionals to utilize output from tools. For example, consider the following workflow:
- Collect data with tool one.
- Collect data with tool two.
- Write code to isolate the data for tool one.
- Write code to isolate and data for tool two.
- Merge data into a standard format.
- Remove duplicated data.
- Expose normalized data.
To summarize, this workflow can be reduced to the following using PyFunnels:
- Specify output files
- Initiate an object.
- Use method on the object.
- Expose normalized data.
PyFunnels has been purposely structured for ease of use and extensibility to new tools and data points. Users of the library are encouraged to contribute code for new tools and data points they find useful. Whenever a user creates Python3 code to isolate data from the output of a tool, he or she is encouraged to commit that code to PyFunnels so others in the community can use it as well.
Metadata
Release files for PyFunnels 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| PyFunnels-0.0.2.tar.gz | 4.3 kB | Without provenance | Details for PyFunnels-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| PyFunnels-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for PyFunnels-0.0.2-py3-none-any.whl |
Total release size: 11.6 kB
Release files / PyFunnels-0.0.2.tar.gz
| Download URL | PyFunnels-0.0.2.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
842cb906ed3b7d9d8555cd7a22365d4fd8bd8adecc64c8f4b66e0eaac00b135c
|
|
BLAKE2b-256 checksum How to use checksums |
e2529655e2ae09eb75a3f4b6e5fba3dca7c048f0740971037caee59fa76e461f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.3
|
Release files / PyFunnels-0.0.2-py3-none-any.whl
| Download URL | PyFunnels-0.0.2-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7d7b5e558f3e632b5064aff3014474fcad1b54afd60c581b949cf070eee7e0ad
|
|
BLAKE2b-256 checksum How to use checksums |
269f81ce4d00b2267d8ab854032f43ad1e07dd914c48c5349cc958d14e91ccf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.3
|
Security for PyFunnels 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.