blindspot

Knowledge resilience report

Repository: /private/tmp/cohort10/langchain
Generated 2026-05-20 13:11 UTC · window: last 90 days · blindspot v0.2.0

Executive brief

Fragile Resilience 48/100 · F · team profile

Top 3 risks
  1. MEDIUM Update CODEOWNERS for .github/ISSUE_TEMPLATE/bug-report.yml .github/ISSUE_TEMPLATE/bug-report.yml
  2. MEDIUM Update CODEOWNERS for .github/ISSUE_TEMPLATE/feature-request.yml .github/ISSUE_TEMPLATE/feature-request.yml
  3. MEDIUM Update CODEOWNERS for .github/PULL_REQUEST_TEMPLATE.md .github/PULL_REQUEST_TEMPLATE.md

Business implication An unexpected departure of the top contributor would orphan 225 critical files and likely slow feature delivery by 3–5 weeks while the team learns the surface.

Executive summary

Establish a successor for Mason Daugherty (mason@langchain.dev)'s work — 225 files would orphan without them

Resilience is **Fragile** (48/100). Weakest dimension: review hygiene (F).

Risk inventory: 225 file(s) would become orphans if the top contributor leaves; 16 file(s) carry high correction load (≥35% fix/revert); 2 service(s) lack AI-readable operational context.

Top recommended action: Establish a successor for Mason Daugherty (mason@langchain.dev)'s work — 225 files would orphan without them

💡 Want a richer, prose-style executive summary? Add a cloud LLM key (Anthropic or OpenAI) to your scan:
--api-key sk-ant-... --provider anthropic --model claude-sonnet-4-6
or set narrative.api_key in .blindspot.yaml. Without a key, this rule-based narrator is used — deterministic, in-process, no network.

Overview

Engineering Resilience Score

Overall
48/100 F
Fragile

Fragile resilience overall (score 48). Weakest dimension: AI operational readiness at 0.

Team-based Multiple maintainers without a single dominant contributor.

Key signals — the six questions

Six concrete questions, each with a one-number answer. This is the report. Everything below is supporting detail; run with --detailed for the deep-dive sections.

Ownership concentration D
1 service rest on a single owner
If that person is unavailable, no one else can confidently change these areas.
Single-engineer dependency
225 files orphan if the top contributor leaves
These files would have no confident owner the day that person walks out.
Knowledge decay
No file is critically decayed
Owners are still close to the code they own.
Review depth
Reviews carry substantive comments
Approvals reflect real scrutiny, not rubber-stamping.
Correction load C
16 files carry a heavy bugfix tail
After each feature these files get a stream of fix/revert commits — stability is paying for delivery pace.
AI-readable context F
Repo lacks AI-readable operational context (1/5)
No specs, architecture notes / ADRs, prompts at the repo root — a new human or AI agent must reverse-engineer the codebase.

Recommended actions

Concrete next steps derived from the signals in this report. Each action is tied to a specific finding — treat them as conversation starters with the team, not directives.

Priority Confidence Category Title Target Evidence
Medium High Codeowners Update Update CODEOWNERS for .github/ISSUE_TEMPLATE/bug-report.yml
Declared owners (@ccurme, @eyurtsev, @mdrxy) do not include the current top contributor. Mason Daugherty (mason@langchain.dev) holds 100% of effective ownership. Either add them to the CODEOWNERS rule or assign explicit cross-coverage.
▸ Declared owner does not include the actual top contributor (Mason Daugherty (mason@langchain.dev) at 100% coverage).
.github/ISSUE_TEMPLATE/bug-report.yml declared=@ccurme, @eyurtsev, @mdrxy, actual_top=mason@langchain.dev, coverage=100%, line=1
Medium High Codeowners Update Update CODEOWNERS for .github/ISSUE_TEMPLATE/feature-request.yml
Declared owners (@ccurme, @eyurtsev, @mdrxy) do not include the current top contributor. Mason Daugherty (mason@langchain.dev) holds 100% of effective ownership. Either add them to the CODEOWNERS rule or assign explicit cross-coverage.
▸ Declared owner does not include the actual top contributor (Mason Daugherty (mason@langchain.dev) at 100% coverage).
.github/ISSUE_TEMPLATE/feature-request.yml declared=@ccurme, @eyurtsev, @mdrxy, actual_top=mason@langchain.dev, coverage=100%, line=1
Medium High Codeowners Update Update CODEOWNERS for .github/PULL_REQUEST_TEMPLATE.md
Declared owners (@ccurme, @eyurtsev, @mdrxy) do not include the current top contributor. Mason Daugherty (mason@langchain.dev) holds 100% of effective ownership. Either add them to the CODEOWNERS rule or assign explicit cross-coverage.
▸ Declared owner does not include the actual top contributor (Mason Daugherty (mason@langchain.dev) at 100% coverage).
.github/PULL_REQUEST_TEMPLATE.md declared=@ccurme, @eyurtsev, @mdrxy, actual_top=mason@langchain.dev, coverage=100%, line=1
Medium High Codeowners Update Update CODEOWNERS for .github/actions/uv_setup/action.yml
Declared owners (@ccurme, @eyurtsev, @mdrxy) do not include the current top contributor. John Kennedy (jkennedyvz@github) holds 100% of effective ownership. Either add them to the CODEOWNERS rule or assign explicit cross-coverage.
▸ Declared owner does not include the actual top contributor (John Kennedy (jkennedyvz@github) at 100% coverage).
.github/actions/uv_setup/action.yml declared=@ccurme, @eyurtsev, @mdrxy, actual_top=jkennedyvz@github, coverage=100%, line=1
Medium High Codeowners Update Update CODEOWNERS for .github/dependabot.yml
Declared owners (@ccurme, @eyurtsev, @mdrxy) do not include the current top contributor. Mason Daugherty (mason@langchain.dev) holds 57% of effective ownership. Either add them to the CODEOWNERS rule or assign explicit cross-coverage.
▸ Declared owner does not include the actual top contributor (Mason Daugherty (mason@langchain.dev) at 57% coverage).
.github/dependabot.yml declared=@ccurme, @eyurtsev, @mdrxy, actual_top=mason@langchain.dev, coverage=57%, line=1