Skip to content

Milestones

List view

  • Code Quality Gates

    Overdue by 6 day(s)
    •
    Due by May 25, 2026
    0% complete0 open0 closed

  • Documentation & DX

    Type annotations, docstrings, and API docs. Work these in alongside feature work as time allows.

    No due date
    •4/8 issues closed
    50% complete4 open4 closed

  • Ruff Cleanup

    Graduated ruff lint cleanup series. Work these in between higher-priority items as time allows.

    No due date
    •1/15 issues closed
    6% complete14 open1 closed

  • v0.5

    Expand open source BlueFlow’s ability to ingest and enrich device data from diverse sources and improve its reliability as the canonical asset repository for hospital device assets. ## Acceptance Criteria BlueFlow ingests device records from at minimum two source types: one passive collector (e.g., Tapirx, Zeek) and one scan-based source (e.g., Nmap, Nessus). File upload supports at least one common asset management export format (e.g., Tenable CSV) with validation and clear error reporting on malformed input. Ingested records are enriched and reconciled against existing inventory — the same physical device does not produce duplicate asset records regardless of ingestion source. Integration backlog is established with stakeholders; at minimum, candidate integrations (Nessus, Nmap, Zeek, Tapirx) are prioritized and the top candidates are in progress or complete. The VIPER webhook payload schema is iterated based on VIPER team feedback; changes are documented and communicated ahead of implementation. REST API endpoints are iterated based on TA feedback; changes are documented and communicated ahead of implementation.

    Due by June 30, 2026
    0% complete0 open0 closed

  • v0.3.0-Hackathon

    Demonstrate Blueflow ingesting Zeek telemetry from a PCAP replay and persisting assets, using a self-contained Docker Compose stack (Zeek + Blueflow + Postgres + Redis). Zeek reads a mounted PCAP and emits conn-shaped JSON observations (IP, ports, L2 when present). The exact fixture protocol is TBD — no HL7 or DICOM assumptions are made here. Blueflow validates a versioned conn-level contract and merges observations into assets; identity and merge rules are MAC-keyed and idempotent across repeated replays. REST surface is scoped to what the compose stack actually needs (assets, token, minimal meta). Full REST audit and cleanup are deferred to post-hackathon. Topology (/api/topology) is a stretch goal — not required for the core PCAP→asset demo.

    Overdue by 9 day(s)
    •
    Due by May 22, 2026
    •10/15 issues closed
    66% complete5 open10 closed