Doorframe

Open source · Local-first

Requirements traceability you can run before the review.

Doorframe turns requirements exports, Jira work items, and test results into a traceability gap report, deterministically and on your own machine. Useful with or without AI.

View on GitHub View on npm Docker

Run it via CLI, npm, or Docker. All local.

Doorframe project dashboard: 42 requirements, 79% fully traced, 19 findings, gap counts by type, and the highest priority findings.
The project dashboard, with the fictional Falcon Telemetry Gateway demo loaded.

Runs locally by default. Doorframe does not send imported project data to any external service.

Tour

From exports to review, in one local app

Import requirements, Jira work items, and JUnit results. Doorframe links them, flags the gaps, and shows you where to look.

Findings page listing errors and warnings such as requirements with no passing linked test evidence, each with a next step.
Findings. Errors first, each with a plain explanation and a recommended next step. Filter by severity or category.
Traceability matrix table showing each requirement with its status, linked work items, linked tests with pass or fail results, and finding count.
Traceability matrix. Every requirement with its work items and test results. Missing links are flagged. Download it as CSV.
Trace graph connecting work items, requirements, and tests, filtered to items that need attention, with a failed test highlighted in red.
Trace graph. Work items, requirements, and tests side by side. Filter to what needs attention or focus on one requirement.
Baseline comparison showing REQ-014 changed from 5 to 2 seconds and flagged high concern, plus added and removed requirements and new and resolved findings.
Baseline diff. Compare two snapshots before a review: changed wording, added and removed requirements, new and resolved findings.

Screenshots show the fictional demo project. Load it yourself with npx doorframe demo.

What it is

A local review tool

  • A local review tool for requirements exports.
  • Available as a CLI, an npm package, or a Docker container. Run it whichever way fits your setup.
  • A deterministic analyzer for traceability gaps, weak wording, duplicate candidates, failed tests, stale links, and closed work without passing verification.
  • A way to compare two requirements baselines before a review.
  • An optional read-only MCP server for local project databases.
  • Works alongside your existing tools (DOORS, Jama, Polarion, Jira, and test management) as a review layer, not a replacement.
  • Runs entirely on your own machine. No SaaS, no accounts, no uploads.

Built for isolated environments

Runs fully air-gapped

  • Once installed, runs entirely on air-gapped and offline networks. No internet connection needed to use it.
  • Makes zero network calls in operation and sends no telemetry. Nothing phones home, nothing to allowlist.
  • Deterministic, repeatable output you can audit. The same inputs always produce the same gap report.
  • Self-hosted on your own hardware. No SaaS, no accounts, no data egress.

The artifact

The thing you actually hand to a review is the HTML traceability gap report. One file. Deterministic. Yours.

Works offline and prints to PDF. Also exports Markdown, a CSV matrix, and JSON.

The generated Doorframe Traceability Report: executive summary counts and a table of top concerns with severity, category, and recommendation.