Replies: 1 comment
-
Just pointing out https://github.com/JetBrains/koog/ as a possible framework here. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I think this is not so hard to implement and could introduce AI into ORT Server.
Motivation
Imagine your repository scans have consistently shown a
status over the past few weeks — even though your team has been pushing new revisions every couple of days. Then, suddenly, the scan status turns to
or
overnight.
Currently, identifying what changed between two revisions of the repository is a manual and time-consuming process. An expert needs to open both reports, compare them side by side, and try to pinpoint what triggered the red status.
Wouldn’t it be helpful if the user interface provided an AI-generated summary in natural language highlighting exactly what changed between the last successful scan and the current one — and likely explaining why the status turned red?
Example AI-generated summary:
What result differences could be part of the AI-generated summary
"In this revision, the Analyzer failed."
"New dependencies to abc:1.2.3 and def:4.5.6 were introduced."
"1 new vulnerability detected (CVE-2023-4567 in json-parser, severity: HIGH)"
"Introduced 1 new policy violation: AGPL-3.0 in experimental-ui-lib."
"A new issue popped up: Provenance for abc:1.2.3 could not be found."
"The execution time for the Analyzer stage doubled from 1 minute to 2 minutes."
... more to be added.
This can be developed step by step, adding more and more result differences over time.
How to implement this?
Beta Was this translation helpful? Give feedback.
All reactions