Replies: 3 comments 1 reply
Triage ReportWe verified each of the 37 issues against the actual source code in the Client SDKS repo. Here's what we found: Hallucinated / False (4 issues)These were fabricated or misunderstood by the scanning tool:
By Design / Not Bugs (6 issues)
Exaggerated (3 issues)
Real Issues Worth FixingHigher Priority
Lower Priority
SummaryOf the 32 "confirmed bugs" in the report, 4 were completely fabricated, 6 are intentional design decisions, and 3 were significantly exaggerated. About 4 are real issues worth prioritizing (2.1, 1.5, 1.2, 3.6), and the remaining ~12 are real but low severity. Tracking IssuesWe've created issues to track the confirmed items:
Thanks again for the report! |
|
Hi @markphelps @erka, I made a further analysis on evaluation-related server APIs (including APIs for server-side SDKs and APIs for client-side SDKs), and Claude Code gives me the following report I think there are some ignorable issues but there are also some real issues (e.g. |
Uh oh!
There was an error while loading. Please reload this page.
Hi @markphelps @erka, I am evaluating Flipt SDKs for Go, and I make a scan with Claude Code, which gives me two reports
From the reports I decided to use server-side SDK instead of the client-side SDK, because the client-side SDK have more issues. I don't have bandwidth to contribute and address these issues, but I hope these reports could be helpful for you. Thanks!
All reactions