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.
65 of your 109 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

speakeasy-api/gram

https://github.com/speakeasy-api/gram · scanned 2026-06-05 20:20 UTC (4 days, 14 hours ago) · 10 languages

1081 raw signals (103 security + 978 graph) 11/13 scanners ran 47th percentile · Typescript · medium (20-100K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 25.0 0.20 5.00
documentation_score 70.0 0.15 10.50
practices_score 69.0 0.15 10.35
code_quality 80.0 0.10 8.00
Overall 1.00 67.8
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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.

Commented-out code 58 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 client/dashboard/vite.config.ts:31
  • info Commented-code block (6 lines) in client/dashboard/src/routes.tsx:352
  • info Commented-code block (6 lines) in client/dashboard/src/components/dev-toolbar.t…
  • info Commented-code block (7 lines) in client/dashboard/src/components/nav-menu.tsx:…
  • info Commented-code block (5 lines) in client/dashboard/src/components/release-stage…
  • info Commented-code block (6 lines) in client/dashboard/src/components/page-layout.t…
  • info Commented-code block (6 lines) in client/dashboard/src/components/page-header.t…
  • info Commented-code block (5 lines) in client/dashboard/src/components/insights-side…
  • info Commented-code block (5 lines) in client/dashboard/src/components/mcp/MCPServer…
  • info Commented-code block (7 lines) in client/dashboard/src/components/ui/multi-sele…
  • info Commented-code block (5 lines) in client/dashboard/src/components/mcp_install_p…
  • info Commented-code block (5 lines) in client/dashboard/src/components/project/Proje…
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 File has no detected symbols: client/dashboard/vite.config.ts
  • low File has no detected symbols: client/dashboard/knip.config.ts
  • low File has no detected symbols: client/dashboard/eslint.config.js
  • low File has no detected symbols: client/dashboard/vitest.config.ts
  • info `truncate` class without `title=` for hover reveal — client/dashboard/src/pages…
  • info Commented-code block (5 lines) in client/dashboard/vite.config.ts:31
  • medium `fetch()` without try/.catch or AbortSignal — elements/src/components/Chat/stor…
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/0e0e6adc-c30f-4993-8ef2-8ec1e775f5b0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0e0e6adc-c30f-4993-8ef2-8ec1e775f5b0/

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.