Skip to main content

Link-Check Report

Purpose

Record link-check policy and latest validation result.

Latest Result — v0.3.0

DateScopeToolResultEvidence
2026-05-18Internal Markdown links and all doc targetsscripts/check_links.py via npm run check:links in CI0 broken internal linksGitHub Actions runs 26051906283 and 26051911199 — both passed
2026-05-16Internal Markdown links (local only)npm run check:links0 broken internal linksLocal stdout — pre-CI baseline
DomainURLHTTP StatusNotes
attack.mitre.orghttps://attack.mitre.org/200 ✓
www.first.orghttps://www.first.org/tlp/200 ✓
oasis-open.github.iohttps://oasis-open.github.io/cti-documentation/200 ✓
www.misp-project.orghttps://www.misp-project.org/documentation/200 ✓
sigmahq.iohttps://sigmahq.io/docs/200 ✓
www.cia.govhttps://www.cia.gov/resources/csi/static/Words-of-Estimative-Probability.pdf200 ✓
www.lockheedmartin.comLM Kill Chain white paper PDF200 ✓
anpa1200.github.ioIsrael CTI project200 ✓
anpa1200.github.ioCustomer CTI project200 ✓
act.globalcyberalliance.orgDiamond Model wiki page403Bot protection / rate limit — page accessible in browser. Monitor; add archive fallback if persistent.

Hard 404s: 0

Transient / bot-blocked: 1 (Diamond Model wiki — accessible in browser, not a dead link)

Validation Policy

  • Internal links must pass CI before merge.
  • Docusaurus build must pass before deploy.
  • Cross-project links should be checked before release, but GitHub Pages propagation can lag immediately after deployment.
  • External source links should record access date in finished products.
  • Critical doctrine references should have archive or fallback references if the original is unstable.

Known Limits

The internal checker validates Markdown link targets in repository docs. It does not prove that every generated Docusaurus route is semantically correct, and it does not certify external websites. External link checks are manual and performed at each release.