Skip to main content

CI Validation Evidence

This page records public GitHub Actions evidence for repository validation and site build health. It complements the README badge and local npm run validate output.

Latest Verified Runs​

Checked on 2026-05-15.

WorkflowCommitStatusConclusionRun URL
Validate CTI Repository559e2cfcompletedsuccesshttps://github.com/anpa1200/israel-government-threat-actors-cti/actions/runs/25923503349
Deploy Docusaurus to GitHub Pages559e2cfcompletedsuccesshttps://github.com/anpa1200/israel-government-threat-actors-cti/actions/runs/25923503386

Validation Scope​

The validation workflow runs:

  • python3 scripts/validate_repo.py
  • python3 scripts/check_source_freshness.py
  • python3 scripts/run_detection_fixture_tests.py
  • python3 scripts/build_detection_dashboard.py
  • npm ci
  • npm run build

The local validation output for the same hardening cycle reported:

Repository validation passed
sources_total=89
sources_stale=0
sources_missing_review_date=0
download_records_total=42
download_records_unavailable=10
DET-001: TP=2 FP=0 TN=4 FN=0 synthetic_fp_rate=0.00%
DET-002: TP=2 FP=0 TN=4 FN=0 synthetic_fp_rate=0.00%
DET-003: TP=2 FP=0 TN=4 FN=0 synthetic_fp_rate=0.00%
DET-004: TP=2 FP=0 TN=4 FN=0 synthetic_fp_rate=0.00%
Docusaurus build passed

The GitHub Actions workflows also opt in to Node.js 24 JavaScript actions execution with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to avoid relying on the deprecated Node.js 20 action runtime.

Interpretation​

CI success proves repository hygiene and site build health. It does not prove that Sigma/KQL rules are production-ready, that detections are tuned, or that the analytics have been validated against customer telemetry. Production claims still require DRL evidence packs.