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.

TKCen/sera

https://github.com/TKCen/sera · scanned 2026-06-16 00:38 UTC (2 months, 1 week ago)

410 raw signals (0 security + 410 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 370 actionable findings from 1 signal source. 40 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 · 370 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 130 Medium 58 Low 131 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 370 Crowd 0 Layer: Software 18 Frontend 48 Network 1 Hardware 23 Security 28 Cicd 4 Quality 74 Api 174

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 2 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.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 29 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 239 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

12 matching findings on this repo

low Stray `console.log` in TS/JS — legacy/verify_schema.ts:14
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…
info `truncate` class without `title=` for hover reveal — legacy/web/src/components/…

View all legacy markers findings →

Commented-out code 12 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/`.

12 matching findings on this repo

info Commented-code block (5 lines) in legacy/tools/bridges/task-router.ts:223
info Commented-code block (9 lines) in legacy/core/agent-runtime/src/contextManager.…
info Commented-code block (12 lines) in legacy/core/agent-runtime/src/__tests__/memo…
info Commented-code block (6 lines) in legacy/core/src/routes/delegation.security.te…
info Commented-code block (5 lines) in legacy/core/src/sandbox/PermissionRequestServ…
info Commented-code block (6 lines) in legacy/core/src/sandbox/ContainerSecurityMapp…
info Commented-code block (5 lines) in legacy/core/src/agents/Orchestrator.ts:176
info Commented-code block (5 lines) in legacy/core/src/agents/process/HierarchicalPr…
info Commented-code block (5 lines) in legacy/core/src/services/vector.service.test.…
info Commented-code block (13 lines) in legacy/core/src/channels/adapters/DiscordAda…
info Commented-code block (5 lines) in legacy/core/src/llm/ContextAssembler.ts:153
info Commented-code block (5 lines) in sdk/typescript/sera-plugin-sdk/scripts/genera…

View all commented-out code findings →

Config drift 6 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.

6 matching findings on this repo

critical Possible secret in rust/crates/sera-config/src/core_config.rs rust/crates/sera-config/src/core_config.rs:347
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: rust/CLAUDE.md rust/CLAUDE.md:143
high Dangling fetch: GET /embedding/config (legacy/web/src/lib/api/embedding.ts:50)
high Dangling fetch: PUT /embedding/config (legacy/web/src/lib/api/embedding.ts:59)
low Unused endpoint: GET /oidc-config

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/1400f4a5-60f7-47cb-8ac5-70dffc67fe70/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1400f4a5-60f7-47cb-8ac5-70dffc67fe70/

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.