Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Task]: Basic PII integration into dashboard #322

Closed
alex-mcgovern opened this issue Feb 14, 2025 · 0 comments · Fixed by #326
Closed

[Task]: Basic PII integration into dashboard #322

alex-mcgovern opened this issue Feb 14, 2025 · 0 comments · Fixed by #326
Assignees

Comments

@alex-mcgovern
Copy link
Collaborator

alex-mcgovern commented Feb 14, 2025

Description

Luke recently merged a PR that introduces PII protections into Codegate: stacklok/codegate#919

This should now be generating alerts when provide a file containing PII to an LLM. (See the relevant dir in the codegate-demonstration repo).

My understanding is that the PII alerts produced should have trigger_type: "codegate-pii" in the JSON blob.

The task here is to:

  • Include PII as one of the "filter tabs"
    Image
  • Include PII in the summary attached to each conversation
    Image
  • Include PII in the "summary block" in the conversation route
    Image
  • Add an empty state for PII into the table's empty state component
    Image

Optional

Longer term, we will probably want to display a tab in the conversation view summarising PII discovered & redacted. However I'm not sure that we have landed on a long-term chosen design for this. The current implementation of the secrets summary is very basic and needs improving.

The concerns around this are:

  • The markdown is not consistent, and repeats redundant information, so it not suited to rendering in a list format
  • There is no structured data around secrets that is returned to be rendered in a list/table format

For PII, these constraints may also apply, I think it's open to interpretation on the best way to integrate this.

Additional Context

No response

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 a pull request may close this issue.

2 participants