kagent-dev/kagent

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

146 of your 511 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 5.34s · analysis 46.75s · 14.3 MB · GitHub API rate-limit (preflight)

https://github.com/kagent-dev/kagent · scanned 2026-06-05 14:31 UTC (5 days, 5 hours ago) · 10 languages

784 raw signals (382 security + 402 graph) 0th percentile · Go · large (100-500K LoC) System graph score 80 (lower by 26)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 5 hours ago · v2 · 347 actionable findings from 2 signal sources. 221 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 142 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	0.0	0.25	0.00
`testing_score`	90.0	0.20	18.00
`documentation_score`	93.6	0.15	14.04
`practices_score`	89.0	0.15	13.35
`code_quality`	17.7	0.10	1.77
Overall		1.00	53.2

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 8 High 101 Medium 42 Low 109 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 205 System graph 142 Crowd 0 Layer: Security 17 Software 188 Cicd 11 Quality 91 Frontend 21 Network 2 Hardware 17

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 6 places

View all duplicates & near-duplicates findings →

Commented-out code 8 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

8 matching findings on this repo

info Commented-code block (7 lines) in ui/src/types/index.ts:607
info Commented-code block (7 lines) in ui/src/lib/messageHandlers.ts:784
info Commented-code block (6 lines) in ui/src/lib/__tests__/AgentsProvider.namespace…
info Commented-code block (5 lines) in python/packages/kagent-adk/src/kagent/adk/typ…
info Commented-code block (6 lines) in python/packages/kagent-adk/src/kagent/adk/_se…
info Commented-code block (9 lines) in python/packages/kagent-adk/src/kagent/adk/_ag…
info Commented-code block (5 lines) in python/packages/kagent-adk/src/kagent/adk/_mc…
info Commented-code block (6 lines) in python/packages/kagent-adk/src/kagent/adk/_re…

View all commented-out code findings →

Config drift 7 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

7 matching findings on this repo

low [COMP001] High cognitive complexity: Function `fetch_well_known_configuration` … python/packages/agentsts-core/src/agentsts/core/c…:16
high [SEC088] Go: TLS InsecureSkipVerify=true: tls.Config{InsecureSkipVerify:true} d… go/adk/pkg/models/tls.go:35
low File has no detected symbols: ui/tailwind.config.ts
low File has no detected symbols: ui/jest.config.ts
low File has no detected symbols: ui/cypress.config.ts
low File has no detected symbols: ui/vitest.config.ts
low File has no detected symbols: ui/next.config.ts

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/79820c95-32a9-4e77-9465-f8dda748c65a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/79820c95-32a9-4e77-9465-f8dda748c65a/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.