Reporting
Output Formats
Each output type serves a different audience: live operator work, shareable narrative reports, or downstream automation.
CLI
Best for live feedback
Readable operator output, findings, and top assets during a run.
TXT
Best for plain sharing
Human-readable offline notes and straightforward report exports.
HTML
Best for reports
Tables, richer summaries, explanatory blocks, and visual report sections.
JSON
Best for tooling
Structured data for automation and downstream processing.
Reporting
Sample Outputs
These examples show exactly what operators can expect to see after a run without needing to imagine the format.
CLI Snapshot
human-readable
asrfrb > scan scanme.nmap.org --passive-only
Scan Overview
-------------
Target: scanme.nmap.org
Subdomains: 2
Open ports: 0
Findings: 0
Recommended Next Steps
----------------------
Use the HTML report for richer offline triage and JSON for automation.
JSON Snapshot
automation
{
"subdomains": [
"scanme.nmap.org",
"nmap.scanme.nmap.org"
],
"generated_at": "2026-04-09T09:16:34Z",
"top_assets": []
}
Relationship Mapping Snapshot
correlation
{
"nodes": [
{"id":"scanme.nmap.org","type":"domain"},
{"id":"45.33.32.156","type":"ip"},
{"id":"scanme.nmap.org:80","type":"service"}
],
"edges": [
{"from":"scanme.nmap.org","to":"45.33.32.156","relation":"resolves_to"},
{"from":"scanme.nmap.org:80","to":"45.33.32.156","relation":"runs_on"}
]
}
Reporting
Configuration
Defaults ship with the framework, while user overrides live outside the repo and installed app folders.
| Path | Role |
|---|---|
config/default.yml | Packaged defaults bundled with the framework |
~/.asrfacet_rb/config.yml | User overrides merged on top of the defaults |
Reporting
Files & Storage
Runtime data is intentionally separated from the repo and installed application files so updates stay cleaner and safer.
| Location | Purpose |
|---|---|
~/.asrfacet_rb/output/ | Report bundles and generated artifacts |
~/.asrfacet_rb/memory/ | Recon memory and historical run state |
~/.asrfacet_rb/web_sessions/ | Saved web-session drafts and state |
/output/ | Repo-local generated output during development runs |
Reporting
Testing
The Rake-based verification flow is the main release gate. The current verified state is 53 examples, 0 failures.
rake
# Full release-style verification
$ bundle exec rake
# Focused targets
$ bundle exec rake spec
$ bundle exec rake test:web
$ bundle exec rake test:install
Current Verified Run
April 9, 2026 — bundle exec rake completed successfully with CLI, web-session, lab, installer, website-installer, and gem-build smoke checks.