Skip to content

fix(ui): New fields don’t automatically update completeness scoring UI#23

Open
afogel wants to merge 1 commit intoGenAI-Security-Project:mainfrom
afogel:dynamic_template_calcuations
Open

fix(ui): New fields don’t automatically update completeness scoring UI#23
afogel wants to merge 1 commit intoGenAI-Security-Project:mainfrom
afogel:dynamic_template_calcuations

Conversation

@afogel
Copy link

@afogel afogel commented Jan 15, 2026

Closes #24

What changed:

  • Use max_points from completeness_score.category_details when displaying per-category points and in the scoring explanation list.
  • Add fixed table layout and column width rules for .category-table to stabilize column sizing and handle long content.

Why:

  • Align the UI with dynamically calculated scoring rules rather than hard-coded point totals.
  • Improve readability and consistency of table layout.

Testing:

  • Not run (template change only).

Suggested next steps:

  1. Quick manual UI check of the results page to confirm table layout and point totals render correctly. You can also review the deployed changes here: https://huggingface.co/spaces/ariel-pillar/OWASP-AIBOM-Generator

@afogel afogel changed the title Render dynamic category point totals in results view fix(ui): New fields don’t automatically update completeness scoring UI Jan 15, 2026
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.

Bug: New fields don’t automatically update completeness scoring UI

1 participant