Skip to content

feat(scripts): validate the published 2026 LLM01-LLM10 entry contract (#168) - #170

Open
drk-ram wants to merge 1 commit into
GenAI-Security-Project:mainfrom
drk-ram:feat/2026-entry-contract-validator
Open

drk-ram wants to merge 1 commit into
GenAI-Security-Project:mainfrom
drk-ram:feat/2026-entry-contract-validator

Conversation

@drk-ram

@drk-ram drk-ram commented Nov 6, 2026

Copy link
Copy Markdown

Summary

Fixes #168.

Adds an offline contract check for the published 2026/final/LLM01–LLM10 entries: pinned titles, the Description, Common Examples of Risk, Prevention and Mitigation Strategies, and Example Attack Scenarios sections, and a refusal of raw script markup. A workflow runs the check on pull requests and pushes to main.

This does not replace the Appendix A crosswalk, permalink, or working-vs-final drift checks in #155, #157, and #167.

Validation

  • python -B .github/scripts/test_validate_entry_contract.py -v — passed, 5 tests
  • python -B .github/scripts/validate_entry_contract.py — OK. 10 published entries match the 2026 contract

Check pinned titles, required sections, and the absence of raw script markup before a release tag is cut.

Fixes GenAI-Security-Project#168

Signed-off-by: Raghuvar Karthik Durga <177662415+drk-ram@users.noreply.github.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.

[Release feedback] Add an offline contract check for published 2026 LLM01-LLM10 entries

1 participant