PROJECT · SECURITY TOOLING

Biuret Reaper.

The proposed Biuret Reaper would turn discovery results into readable device context and practical reports. The current code is experimental planning work.

Future concept · experimental code · no product release

STATUS FUTURE CONCEPT
FORMAT DESKTOP TOOL
BOUNDARY AUTHORIZED USE
LAST UPDATEDOCT 2026
CONCEPT SUMMARY

Network discovery with clearer signals.

Biuret Reaper explores how authorized network discovery can present useful signals without turning the interface into an overwhelming wall of technical output.

PLANNED FEATURES

Designed for useful results.

Focused discovery

Planned capability: Scanning workflows are organized around practical visibility and deliberate user control.

Device context

Planned capability: Selected signals are combined into a clearer summary of discovered devices and services.

Responsive workflow

Planned capability: Clear progress and cancellation states keep longer discovery tasks understandable and manageable.

THE USER JOURNEY

A useful problem comes first.

Who would use it?

Owners of small authorized labs who need an understandable inventory of hosts and exposed services.

The problem to solve

Raw discovery output does not explain scope or uncertainty. Results should show what was checked, what responded and what remains unknown.

A proposed everyday flow

Confirm an authorized range, run bounded discovery, review host and service observations and export a report. An open service is not proof of a vulnerability.

NEXT IMPLEMENTATION STEPS

A plan to validate, then build.

Proposed milestones, not completed deliverables.

  1. Define authorization and scope

    Make the target range and scan limits explicit before collecting data.

  2. Build a bounded lab prototype

    Start with a small test network, cancellation controls and conservative rate limits.

  3. Review reliability and reporting

    Test timeouts, partial results and report clarity without overstating discovery accuracy.

Project status: This page is a future product plan. Repository code is experimental and does not represent a released, validated, or deployment-ready application.