Skip to content

feat:added severity badge in event row and remove payload from event api#44

Open
Adarsh9977 wants to merge 2 commits into
secureagentics:mainfrom
Adarsh9977:severity-badge
Open

feat:added severity badge in event row and remove payload from event api#44
Adarsh9977 wants to merge 2 commits into
secureagentics:mainfrom
Adarsh9977:severity-badge

Conversation

@Adarsh9977

Copy link
Copy Markdown
Contributor

Summary

  • Add latest verdict metadata to the event list API response without including heavy event payload or token fields.
  • Show severity badges in the Events table and mobile cards based on MAD codes.
  • Keep the event list API lightweight by omitting full payload/token fields from list rows, while still loading full event details on demand when a row is expanded.

Test plan

  • Added backend coverage confirming event list items omit payload/token fields and include latest verdict data.

Screenshot (UI changes only)

Screenshot 2026-06-10 at 2 27 02 AM

Checklist

  • CLA signed (see CLA.md)
  • Tests pass locally
  • Docs updated where needed
  • British English; no em-dashes; no marketing fluff

@Adarsh9977 Adarsh9977 changed the title added severity badge and remove payload from event api feat:added severity badge in event row and remove payload from event api Jun 9, 2026
@yanny-sec

Copy link
Copy Markdown
Contributor

Thanks Adarsh. One small nit:

EventListRow.PayloadJSON/TokensUsed are now unreachable in ListEvents. ListEvents stopped selecting them, so they're always empty for list rows (only GetEvent fills them now). Harmless, but a comment or a split type would stop a future caller trusting empty fields.

Rest looks good, thanks!

@Adarsh9977

Copy link
Copy Markdown
Contributor Author

@yanny-sec Thanks, done with the split of eventList with eventListDetail

Thanks Adarsh. One small nit:

EventListRow.PayloadJSON/TokensUsed are now unreachable in ListEvents. ListEvents stopped selecting them, so they're always empty for list rows (only GetEvent fills them now). Harmless, but a comment or a split type would stop a future caller trusting empty fields.

Rest looks good, thanks!

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.

2 participants