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.
Sign up free Scan another repo

tbfl76z/saju-app

https://github.com/tbfl76z/saju-app · scanned 2026-06-16 00:30 UTC (2 months, 2 weeks ago)

88 raw signals (0 security + 88 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 87 actionable findings from 1 signal source. 1 repeated signal grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
76.0
/100
Security checks
76
0 findings
System graph
76
100.0% cov · 87 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 14 Medium 11 Low 56 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 87 Crowd 0 Layer: Software 24 Frontend 5 Hardware 3 Security 16 Cicd 1 Quality 14 Api 24
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 76.0/100 with 100.0% coverage. It contains 527 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 88 findings — concentrated in software (24), api (24), security (16). Risk profile is high: 0 critical, 14 high, 11 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 81 of 87 actionable findings. 88 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security auth conf 1.00 FastAPI POST `analyze_stream` without auth dependency — backend-fastapi/main.py:385
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:385 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `analyze` without auth dependency — backend-fastapi/main.py:373
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:373 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `calculate` without auth dependency — backend-fastapi/main.py:117
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:117 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `compatibility` without auth dependency — backend-fastapi/main.py:244
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:244 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_share` without auth dependency — backend-fastapi/main.py:317
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:317 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `ilun` without auth dependency — backend-fastapi/main.py:224
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:224 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `image_prompt` without auth dependency — backend-fastapi/main.py:358
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:358 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `learn_backup` without auth dependency — backend-fastapi/main.py:453
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:453 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `learn_grade` without auth dependency — backend-fastapi/main.py:502
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:502 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `learn_personal_quiz` without auth dependency — backend-fastapi/main.py:429
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:429 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `learn_tutor` without auth dependency — backend-fastapi/main.py:542
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:542 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `newyear` without auth dependency — backend-fastapi/main.py:288
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:288 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `seyun` without auth dependency — backend-fastapi/main.py:177
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:177 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `wolun` without auth dependency — backend-fastapi/main.py:199
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend-fastapi/main.py:199 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend-next/src/components/DailyFortune.tsx:89
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend-next/src/lib/analyzeStream.ts:65
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend-next/src/lib/learn.ts:89
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend-fastapi/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend-fastapi/main.py:88
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
backend-fastapi/main.py:88 Cors wildcard
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 17 placeholder/mock markers across 10 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 68 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 24 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend-fastapi/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend-fastapi/saju_utils.py:calculate_daeun_number, backend-fastapi/saju_utils.py:calculate_daeun This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `learn_backup` in backend-fastapi/main.py:454
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: analysis_callback
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:920
low System graph software Dead code conf 1.00 Possibly dead Python function: calendar_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:681
low System graph software Dead code conf 1.00 Possibly dead Python function: day_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:728
low System graph software Dead code conf 1.00 Possibly dead Python function: format_pillar
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:67
low System graph software Dead code conf 1.00 Possibly dead Python function: gender_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:666
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_calendar_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1226
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_cancel
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1449
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_day_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1268
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_gender_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1210
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_hour_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1286
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_minute_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1304
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_month_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1254
low System graph software Dead code conf 1.00 Possibly dead Python function: gh_year_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1240
low System graph software Dead code conf 1.00 Possibly dead Python function: gunghap_start
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1191
low System graph software Dead code conf 1.00 Possibly dead Python function: gunghap_start_callback
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:1174
low System graph software Dead code conf 1.00 Possibly dead Python function: help_command
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:591
low System graph software Dead code conf 1.00 Possibly dead Python function: hour_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:748
low System graph software Dead code conf 1.00 Possibly dead Python function: minute_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:768
low System graph software Dead code conf 1.00 Possibly dead Python function: month_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:712
low System graph software Dead code conf 1.00 Possibly dead Python function: name_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:654
low System graph software Dead code conf 1.00 Possibly dead Python function: saju_start
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:643
low System graph software Dead code conf 1.00 Possibly dead Python function: start_command
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:574
low System graph software Dead code conf 1.00 Possibly dead Python function: term_command
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:612
low System graph software Dead code conf 1.00 Possibly dead Python function: year_received
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
backend-fastapi/telegram_bot.py:696
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`backend-fastapi/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/dashboard
`backend-fastapi/main.py` declares `GET /admin/dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /admin/stats
`backend-fastapi/main.py` declares `GET /admin/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /learn/backup/{code}
`backend-fastapi/main.py` declares `GET /learn/backup/{code}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /learn/chapter/{chapter_id}
`backend-fastapi/main.py` declares `GET /learn/chapter/{chapter_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /learn/curriculum
`backend-fastapi/main.py` declares `GET /learn/curriculum` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /learn/placement
`backend-fastapi/main.py` declares `GET /learn/placement` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /learn/quiz/{chapter_id}
`backend-fastapi/main.py` declares `GET /learn/quiz/{chapter_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /share/{code}
`backend-fastapi/main.py` declares `GET /share/{code}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /terms
`backend-fastapi/main.py` declares `GET /terms` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /analyze
`backend-fastapi/main.py` declares `POST /analyze` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /analyze/stream
`backend-fastapi/main.py` declares `POST /analyze/stream` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /calculate
`backend-fastapi/main.py` declares `POST /calculate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /compatibility
`backend-fastapi/main.py` declares `POST /compatibility` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /ilun
`backend-fastapi/main.py` declares `POST /ilun` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /image-prompt
`backend-fastapi/main.py` declares `POST /image-prompt` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /learn/backup
`backend-fastapi/main.py` declares `POST /learn/backup` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /learn/grade
`backend-fastapi/main.py` declares `POST /learn/grade` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /learn/quiz/personal
`backend-fastapi/main.py` declares `POST /learn/quiz/personal` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /learn/tutor
`backend-fastapi/main.py` declares `POST /learn/tutor` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /newyear
`backend-fastapi/main.py` declares `POST /newyear` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /seyun
`backend-fastapi/main.py` declares `POST /seyun` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /share
`backend-fastapi/main.py` declares `POST /share` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /wolun
`backend-fastapi/main.py` declares `POST /wolun` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: backend-fastapi/telegram_bot.py (1535 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/f28bcf77-4b16-488b-a70d-164790c8e953/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f28bcf77-4b16-488b-a70d-164790c8e953/

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.