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

rounakjain2604/fr-study-os

https://github.com/rounakjain2604/fr-study-os · scanned 2026-06-15 23:56 UTC (2 months, 3 weeks ago)

31 raw signals (0 security + 31 graph)

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

Complete repo analysis

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

JSON
Combined
74.5
/100
Security checks
75
0 findings
System graph
75
77.8% cov · 31 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 0 Medium 21 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 31 Crowd 0 Layer: Frontend 1 Security 11 Cicd 1 Quality 15 Api 3
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 74.5/100 with 77.8% coverage. It contains 400 nodes across 3 cross-layer flows, written primarily in mixed languages. Engine surfaced 31 findings — concentrated in quality (15), security (11), api (3). Risk profile is low: 0 critical, 0 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 28 of 31 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — app/src/components/ChapterDashboard.tsx:12
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app/src/lib/sync.ts:119
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 — worker/src/index.mjs:302
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 Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/launch.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 security security conf 1.00 Insecure pattern 'cors_wildcard' in worker/src/index.mjs:289
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
worker/src/index.mjs:289 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in app/src/components/ChapterDashboard.tsx:12
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
app/src/components/ChapterDashboard.tsx:12 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app/public/content/ind_as_109_unit2_dashboard.html:4036
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app/public/content/ind_as_109_unit2_dashboard.html:4036 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in app/public/content/Ind_AS_23_Borrowing_Costs_Dashboard_polished.html:941
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
app/public/content/Ind_AS_23_Borrowing_Costs_Dashboard_polished.html:941 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in reference/legacy-dashboards/fr-45day-tracker-v2.html:342
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
reference/legacy-dashboards/fr-45day-tracker-v2.html:342 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in reference/legacy-dashboards/ind_as_109_unit1_notes.html:2198
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
reference/legacy-dashboards/ind_as_109_unit1_notes.html:2198 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in reference/legacy-dashboards/ind_as_109_unit2_dashboard.html:4036
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
reference/legacy-dashboards/ind_as_109_unit2_dashboard.html:4036 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in reference/legacy-dashboards/Ind_AS_23_Borrowing_Costs_Dashboard_polished.html:941
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
reference/legacy-dashboards/Ind_AS_23_Borrowing_Costs_Dashboard_polished.html:941 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in reference/study-os-prototype/src/app.js:93
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
reference/study-os-prototype/src/app.js:93 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in app/scripts/deploy-pages.mjs:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
app/scripts/deploy-pages.mjs:3 Node child process
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 12 placeholder/mock markers across 5 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 42 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 8 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BASE_URL`, `GEMINI_MODEL`, `GOOGLE_API_KEY`, `GROQ_MODEL`, `HOST`, `MISTRAL_MODEL`, `OPENROUTER_MODEL`, `PROD`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.
config drift
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 14 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 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 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 /api/health
`ai-server/server.mjs` declares `GET /api/health` 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 /api/ai
`ai-server/server.mjs` declares `POST /api/ai` 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 /api/ai-tutor
`ai-server/server.mjs` declares `POST /api/ai-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
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/70c24f43-cc5b-4a5c-8249-0fafe6a1133c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/70c24f43-cc5b-4a5c-8249-0fafe6a1133c/

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.