{
  "type": "failure-mode",
  "name": "Adopting a fork whose maintenance has stopped",
  "slug": "adopting-a-fork-whose-maintenance-has-stopped",
  "section": {
    "id": "frameworks",
    "number": "02",
    "title": "Choosing a framework",
    "url": "https://zkpick.com/frameworks/"
  },
  "url": "https://zkpick.com/frameworks/failure-modes/adopting-a-fork-whose-maintenance-has-stopped/",
  "markdown": "https://zkpick.com/md/frameworks/failure-modes/adopting-a-fork-whose-maintenance-has-stopped.md",
  "detail": "A widely used fork is chosen because a lot of existing code depends on it, then turns out to be in declared maintenance mode — feature and architectural changes are no longer reviewed — so the team silently inherits responsibility for future security patches.",
  "mitigation": "Check the maintenance posture of the specific fork, not the upstream project. If it is in maintenance mode, budget for owning it or choose differently for greenfield work.",
  "relatedOptions": [],
  "updated": "2026-09-12",
  "version": "1.3",
  "canonical": "https://zkpick.com/frameworks/failure-modes/adopting-a-fork-whose-maintenance-has-stopped/",
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "authors": [
    "MarketComp"
  ]
}