SARF CLI
Add the output of a tool to SARF
The output of any console tool can be redirected to sarf. It doesn't matter if
these are in plain text or binary.
In order for sarf to prepare to receive the output of a tool, the --ingest
flag must be added to it.
nmap 192.168.1.0/24 | sarf --ingest --tags nmap,network:192.168.1.0 --report lbk
--tags flag is optional. It adds tags to the received data that can be
very useful to interconnect with other tools.
The received data must be associated with a report.
The chosen report will be obtained from the environment variable SARF_REPORT.
The chosen report can also be provided explicitly with the --report flag.
This is all for now. SARF is at a very early stage of its development. Give it a star on github to find out all its progress.
1 maintainer
Metadata
1 maintainer
Release files for sarf 0.3.0
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 | |
|---|---|---|---|---|
| sarf-0.3.0.tar.gz | 12.1 kB | Without provenance | Details |
Release files / sarf-0.3.0.tar.gz
| Download URL | sarf-0.3.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63425f2755c46333eee3c9b290a7d8e05b589c99da235fd71699aa8f56b2c89e
|
|
BLAKE2b-256 checksum How to use checksums |
a6e72b96fdb0007a5088cddb73e17ce5feb7385fbe580da7c5b798c6d0648b3f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for sarf 0.3.0
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.
