Repository navigation
feat(llm-app-review): record the OWASP LLM category in owasp_llm_references - #290
Merged
Merged
Conversation
…rences traust-core now carries owasp_llm_references on report findings and stores each category as an owasp-llm finding label, so the checklist records the category in the structured field again; the check number stays in the description. Pins traust-core#228. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chubirka The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
…cts#89) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
openshift-ci
Bot
added
the
needs-rebase
…-references-record # Conflicts: # pyproject.toml # uv.lock
openshift-ci
Bot
removed
the
needs-rebase
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The LLM application checklist records a finding's OWASP LLM Top 10 category in the structured field again (Vercel comparison gap plan, OWASP storage option A).
llm-application-review.md: report findings carry the category inowasp_llm_references(for example["LLM06"]); the check number stays in thedescription./vuln-scanfindings have no reference fields, so they keep naming the category and check number in the description. This restores the wordingmainalready uses.d451649), which carriesowasp_llm_referenceson findings and stores each category as afinding_labelrow with taxonomyowasp-llm. It brings traust-contracts#88 (the schema field and theowasp-llm-categoryenum, merged), and through core development traust-core#232 with traust-contracts#89: uppercase roadmap prioritiesP0–P4record asp0–p4.tests/test_llm_app_review.py: the field-names test now requiresowasp_llm_references, and a new test checks that the schema field takes exactly LLM01–LLM10, the categories the checklist covers.CHANGELOG.md[Unreleased]entries for both.Verification
Merge order: traust-contracts#89 → traust-core#228 → this (re-pin to the merged core commit if needed).
🤖 Generated with Claude Code