Skip to content

Correct scanning workflow history and timing claims - #633

Merged
williamzujkowski merged 1 commit into
mainfrom
fix/scanning-vestiges
Sep 13, 2026
Merged

Correct scanning workflow history and timing claims#633
williamzujkowski merged 1 commit into
mainfrom
fix/scanning-vestiges

Conversation

@williamzujkowski

Copy link
Copy Markdown
Owner

The scanning article described three incompatible job orders and still called the aggregate gate unimplemented. Inspection of the canonical gist's three dated revisions shows that its original November 2025 gate was an echo-only stub, while the August 18 and August 23, 2026 revisions check all three job results. The article now dates that correction, labels the old snippet as historical, and explains OSV-first followed by independent Grype/Trivy jobs. It also corrects the adjacent claim that every action is commit-pinned: checkout and SARIF upload still use version tags.

The performance table now labels its total as a sum of reported scanner durations and fixes the sum to 117 seconds. The 70% reduction is arithmetic on those listed figures, not a new benchmark. Historical timings, optimization savings and runner attribution are explicitly unverified because no retained timing evidence was found. No end-to-end workflow time is inferred from the dependency graph. The original post URL/date remain, with a September 13 correction and lastUpdate.

Validation: final production build passed; Astro check reported 0 errors and 0 warnings (7 existing hints); required pre-commit build passed. Source revisions, GitHub job semantics, scope and arithmetic are recorded in docs/research/2026-09-13-scanning-vestigial-review.md. No gist or mirror was changed.

Closes #632.

@williamzujkowski
williamzujkowski merged commit 6eeb108 into main Sep 13, 2026
15 checks passed
@github-actions

Copy link
Copy Markdown

⚠️ Link Validation Results

  • Total Links: 1009
  • Broken Links: 2
  • Status: warning
View Full Report

Link Validation Report

Generated: 2026-09-13T06:34:17

Validation results (unique URLs): 1009
Extracted link occurrences: 1547
Extracted occurrences with a verdict: 1547
Unchecked extracted occurrences: 0
Checked URLs without extracted source metadata: 0
Review entries: 119 (extracted occurrences plus checked URLs without source metadata)

Result Checked unique URLs Extracted occurrences
Valid 822 1220
Confirmed broken 2 2
Redirects 0 0
Needs manual verification 87 115
Access-restricted 0 0
Timeouts 2 2
Errors 0 0
Unchecked 0 0
Internal (checked separately) 79 184
Placeholder (not checked online) 17 24
Total 1009 1547

Verification incomplete. Unresolved and unchecked results are advisory; they do not establish that a link is broken.

See manual_review.md for every review entry and source location, detailed_report.csv for all results, and action_plan.md for supervised follow-up. No repairs are applied by this workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove stale parallelism and gate claims from the scanning-pipeline article

1 participant