upstash/context7

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.

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

Scan timing: clone 8.23s · analysis 19.19s · 16.4 MB · GitHub preflight 487ms

https://github.com/upstash/context7 · scanned 2026-06-05 10:00 UTC (5 days, 16 hours ago) · 10 languages

332 raw signals (164 security + 168 graph) 38th percentile · Typescript · small (2-20K LoC) System graph score 56 (higher by 8)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 16 hours ago · v2 · 166 actionable findings from 2 signal sources. 82 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 · 63 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	45.8	0.25	11.45
`testing_score`	79.0	0.20	15.80
`documentation_score`	64.0	0.15	9.60
`practices_score`	72.0	0.15	10.80
`code_quality`	71.0	0.10	7.10
Overall		1.00	63.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 35 Medium 49 Low 61 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 103 System graph 63 Crowd 0 Layer: Software 120 Cicd 7 Quality 13 Security 8 Frontend 12 Hardware 3 Api 3

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.

Commented-out code 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (5 lines) in packages/mcp/src/index.ts:503

View all commented-out code findings →

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

12 matching findings on this repo

medium GitHub Action `aws-actions/configure-aws-credentials@v5` is 1 major version(s) … .github/workflows/ecr-deploy.yml:20
info npm package `eslint-config-prettier` is patch version(s) behind (^10.1.1 -> 10.… package.json
low File has no detected symbols: eslint.config.js
low File has no detected symbols: packages/pi/eslint.config.js
low File has no detected symbols: packages/pi/vitest.config.ts
low File has no detected symbols: packages/mcp/eslint.config.js
low File has no detected symbols: packages/cli/tsup.config.ts
low File has no detected symbols: packages/cli/eslint.config.js
low File has no detected symbols: packages/cli/vitest.config.ts
low File has no detected symbols: packages/tools-ai-sdk/tsup.config.ts
low File has no detected symbols: packages/tools-ai-sdk/eslint.config.js
low File has no detected symbols: packages/tools-ai-sdk/vitest.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/c1b43730-b3d0-4cb5-b932-51efa221260d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c1b43730-b3d0-4cb5-b932-51efa221260d/

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.