Show the Endor id in the published tables - #7
Merged
Conversation
endor_id is set from the moment a record exists, but only the pending table rendered it. The published tables read refs.endor, a transparency-page URL that often lands later or never, so a record's Endor id disappeared at exactly the point it went public: CVE-2026-27959 carries ENDOR-VUL-2026-2301 and its Endor Reference cell showed a dash. Both tables and the detail page now render the id as the visible text, and upgrade it to a link once refs.endor exists, so the same text stays in place either way. A record with only a URL still falls back to the "Endor" label, and one with neither still renders a dash. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
CVE-2026-27959carriesendor_id: ENDOR-VUL-2026-2301, but its Endor Reference cell rendered a dash.Cause
The schema has two separate Endor concepts, and only one of them ever reached the published tables:
endor_idrefs.endorSo a record's Endor id disappeared at exactly the point it went public. The value was stored and validating correctly the whole time — it just had no render path for
status: published.All four GT Edge findings showed a dash there too; the column had never rendered anything.
Change
_endor_reference()in the HTML renderer, mirrored in the README renderer:endor_idis the visible textrefs.endorexists — same text either way, so adding the URL later changes nothing visually except the linkEndorlabel, as beforeNo record data changed; this is renderer-only.
Result
Verification
pytest -q— 157 passed (152 before, 5 new)generateexit 0;generate --checkexit 0; second run byte-identicalendor_idstill render dashesNote
In the README the Endor id lands in the Links column, so that column now holds one entry that is plain text rather than a link until the transparency URL exists. The site table has a dedicated Endor Reference column and doesn't have this wrinkle. Easy to drop the README half if you'd rather that column stayed links-only.
🤖 Generated with Claude Code