Skip to content

Fix the two external links failing link check since 2026-09-28 - #180

Merged
emmanuelgjr merged 1 commit into
mainfrom
fix/link-check
Oct 1, 2026
Merged

emmanuelgjr merged 1 commit into
mainfrom
fix/link-check

Conversation

@emmanuelgjr

Copy link
Copy Markdown
Contributor

The link check on main has failed since 922350d (2026-09-28) on two external links. Neither is caused by a change in this repo.

1. layerxsecurity.com (403). Akamai announced its acquisition of LayerX on 2026-05-14, and the product is now Akamai Workforce Protector. The old domain redirects there. The DSGAI16 tool row in DSGAI_ISO27001.md and DSGAI_NISTAIRMF.md is renamed "Akamai Workforce Protector (formerly LayerX)" and repointed, then regenerated (DSGAI16.json, docs/data.js). Akamai answers 403 to any non-browser client regardless of user agent, so it is excluded in lychee.toml with that reason, as the file's policy requires.

2. SCF 2026.2 spreadsheet (404). SCF replaced the file with 2026.3 on 2026-09-21. docs/COMPETITIVE_ANALYSIS.md cites figures computed from 2026.2 (1,534 controls, 161 AAT), so ref [22] is pinned to the 2026.2 commit (51528d2, verified 200) rather than repointed at a release the figures don't come from.

Local: validate 0 errors, stats:check current, 89/89 tests.

🤖 Generated with Claude Code

- LayerX was acquired by Akamai (announced 2026-05-14) and the product
  renamed Akamai Workforce Protector; layerxsecurity.com now redirects to
  an Akamai page that answers 403 to the checker. Renamed the DSGAI16
  tool row in the ISO 27001 and NIST AI RMF files and pointed it at the
  product page, then regenerated. Akamai is excluded in lychee.toml with
  its reason, as the file's policy requires.
- SCF moved its spreadsheet from 2026.2 to 2026.3 on main. The
  competitive analysis cites figures computed from 2026.2, so ref [22]
  is pinned to the 2026.2 commit rather than repointed at a release
  those figures did not come from.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@emmanuelgjr
emmanuelgjr merged commit a34fdbe into main Oct 1, 2026
6 checks passed
@emmanuelgjr
emmanuelgjr deleted the fix/link-check branch October 1, 2026 02:43
emmanuelgjr pushed a commit that referenced this pull request Oct 1, 2026
…10 URL in two files

Found by a local lychee 0.24.2 run with lychee.toml after #180. The CI
link check passes on main, but these return 404 to an ordinary browser:

- CONTRIBUTING.md: OWASP moved its policies to policy.owasp.org. The new
  page is the same document as OWASP/www-policy
  operational/code-of-conduct.md ("Adopted by the Board of Directors on
  September 25, 2024").
- Agentic_COSAI.md, Agentic_GPAICOP.md (both from #34): used
  /resource/agentic-ai-top-10/. The other 22 Agentic files already use
  /resource/owasp-top-10-for-agentic-applications-for-2026/ (200). The
  line is rewrapped the way Agentic_AITG.md does it, to stay within MD013.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
emmanuelgjr added a commit that referenced this pull request Oct 1, 2026
…10 URL in two files (#181)

Found by a local lychee 0.24.2 run with lychee.toml after #180. The CI
link check passes on main, but these return 404 to an ordinary browser:

- CONTRIBUTING.md: OWASP moved its policies to policy.owasp.org. The new
  page is the same document as OWASP/www-policy
  operational/code-of-conduct.md ("Adopted by the Board of Directors on
  September 25, 2024").
- Agentic_COSAI.md, Agentic_GPAICOP.md (both from #34): used
  /resource/agentic-ai-top-10/. The other 22 Agentic files already use
  /resource/owasp-top-10-for-agentic-applications-for-2026/ (200). The
  line is rewrapped the way Agentic_AITG.md does it, to stay within MD013.

Co-authored-by: sim <sim@local>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant