animesh0911/qs-paper-generator — Repobility public scan

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

animesh0911/qs-paper-generator

https://github.com/animesh0911/qs-paper-generator · scanned 2026-06-17 01:34 UTC (1 month, 2 weeks ago)

79 raw signals (0 security + 79 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -22.8 (diff) · 71 actionable findings from 1 signal source. 8 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

Security checks

100.0% cov · 71 findings

click to filter

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 4 Medium 27 Low 36 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 71 Crowd 0 Layer: Hardware 4 Security 8 Cicd 1 Quality 38 Api 20

Exclude dismissed / FP Exclude test files

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 53.9/100 with 100.0% coverage. It contains 1540 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 79 findings — concentrated in quality (46), api (20), security (8). Risk profile is high: 1 critical, 4 high, 29 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 68 of 71 actionable findings. 79 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.

critical System graph security Secrets conf 1.00 Possible secret in backend/bank/management/commands/seed_questions.py

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

backend/bank/management/commands/seed_questions.py:195

high System graph api Wiring conf 1.00 Dangling fetch: GET /api${path} (frontend/src/lib/api.ts:48)

`frontend/src/lib/api.ts:48` calls `GET /api${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/api/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET /papers/${id}/ (frontend/src/lib/api.ts:100)

`frontend/src/lib/api.ts:100` calls `GET /papers/${id}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/papers/<p>` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /papers/${id}/pdf/ (frontend/src/lib/api.ts:148)

`frontend/src/lib/api.ts:148` calls `GET /papers/${id}/pdf/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/papers/<p>/pdf` If this points at an external API, prefix it with `https://` so the matcher skips …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /papers/${id}/approve/ (frontend/src/lib/api.ts:121)

`frontend/src/lib/api.ts:121` calls `POST /papers/${id}/approve/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/papers/<p>/approve` If this points at an external API, prefix it with `https://` so the match…

Dangling fetchHelper:request

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/code-review/SKILL.md

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/skills/code-review/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/diagnose/SKILL.md

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/skills/diagnose/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/grill-with-docs/SKILL.md

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/skills/grill-with-docs/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/prototype/LOGIC.md

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/skills/prototype/LOGIC.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/prototype/SKILL.md

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/skills/prototype/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/prototype/UI.md

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/skills/prototype/UI.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/setup-matt-pocock-skills/issue-tracker-github.md

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/skills/setup-matt-pocock-skills/issue-tracker-github.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/setup-matt-pocock-skills/issue-tracker-gitlab.md

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/skills/setup-matt-pocock-skills/issue-tracker-gitlab.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/setup-matt-pocock-skills/issue-tracker-local.md

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/skills/setup-matt-pocock-skills/issue-tracker-local.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/setup-matt-pocock-skills/SKILL.md

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/skills/setup-matt-pocock-skills/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/tdd/SKILL.md

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/skills/tdd/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/triage/AGENT-BRIEF.md

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/skills/triage/AGENT-BRIEF.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/triage/SKILL.md

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/skills/triage/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .mcp.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.

.mcp.json VerificationMcp config

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. 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 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 auth conf 1.00 Django view `chapter_map_node_details` may be unauthenticated — backend/corpus/views.py:39

Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.

backend/corpus/views.py:39 securityAuth django unauth view

medium System graph security auth conf 1.00 Django view `chapter_map` may be unauthenticated — backend/corpus/views.py:21

Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.

backend/corpus/views.py:21 securityAuth django unauth view

medium System graph security auth conf 1.00 Django view `chapters` may be unauthenticated — backend/bank/views.py:48

Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.

backend/bank/views.py:48 securityAuth django unauth view

medium System graph security auth conf 1.00 Django view `ingest_status` may be unauthenticated — backend/bank/views.py:81

Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.

backend/bank/views.py:81 securityAuth django unauth view

medium System graph security auth conf 1.00 Django view `ingest` may be unauthenticated — backend/bank/views.py:55

Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.

backend/bank/views.py:55 securityAuth django unauth view

medium System graph security auth conf 1.00 Django view `metadata` may be unauthenticated — backend/bank/views.py:32

Function-view with `request` parameter has no `@login_required` or equivalent auth decorator within 5 lines above. If auth is enforced by middleware (`AUTHENTICATION_BACKENDS`), this is a false positive — dismiss with reason `by_design`.

backend/bank/views.py:32 securityAuth django unauth view

medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph quality Integrity conf 1.00 3 occurrences Frontend route `/editor` has no Link/navigate to it — frontend/src/App.tsx

The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.

3 occurrences

repo-level (3 hits)

Orphan pageWiring

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 quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 39 placeholder/mock markers across 17 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `DEV`, `GEMINI_THINKING_BUDGET`, `LLM_MAX_RETRIES`, `LLM_PROVIDER`, `VITE_API_PROXY`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

frontend/Dockerfile:1 containersPinned dependencies

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/Dockerfile:1 containersPinned dependencies

low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: backend/papers/views.py:post, backend/papers/views.py:post 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 separate.

6 occurrences

repo-level (6 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: backend/corpus/retrieval.py:retrieve, backend/corpus/retrieval.py:retrieve, backend/corpus/retrieval.py:retrieve This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or documen…

2 occurrences

repo-level (2 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places

Functions with the same first-5-line body hash: backend/papers/views.py:get, backend/papers/views.py:get, backend/papers/views.py:get, backend/papers/views.py:get This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docum…

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 `cbse_science_class_10_board_compact_2026_v1` in backend/papers/document.py:121

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 quality Integrity conf 1.00 Old/deprecated-named symbol `cbse_science_class_10_board_compact_2026_v1` in backend/papers/migrations/0008_seed_paperformat.py:7

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 quality Integrity conf 1.00 Old/deprecated-named symbol `cbse_science_class_10_board_compact_2026_v1` in backend/papers/tests/test_builder.py:395

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 quality Integrity conf 1.00 Old/deprecated-named symbol `cbse_science_class_10_board_compact_2026_v1` in frontend/src/hooks/useCoverageForm.hook.test.ts:13

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 quality Integrity conf 1.00 Old/deprecated-named symbol `cbse_science_class_10_board_compact_2026_v1` in frontend/src/lib/api.test.ts:39

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 quality Integrity conf 1.00 Old/deprecated-named symbol `cbse_science_class_10_board_compact_2026_v1` in frontend/src/lib/paper-format-renderers/cbse-compact-renderer.ts:5

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 quality Integrity conf 1.00 Old/deprecated-named symbol `cbse_science_class_10_board_compact_2026_v1` in frontend/src/mocks/paper-document-v1.mock.ts:12

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 quality Integrity conf 1.00 Old/deprecated-named symbol `cbse_science_class_10_board_compact_2026_v1` in frontend/src/types/paper-document.schema.test.ts:11

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 quality Integrity conf 1.00 Old/deprecated-named symbol `qpg_mock_print_document_v1` in frontend/src/lib/mock-paper-document-storage.ts:20

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 quality Integrity conf 1.00 Old/deprecated-named symbol `unknown_format_v1` in frontend/src/lib/paper-format-renderers.test.ts:35

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 cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph api Wiring conf 1.00 Unused endpoint: ANY /admin/

`backend/config/urls.py` declares `ANY /admin/` 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: ANY /api/auth/

`backend/config/urls.py` declares `ANY /api/auth/` 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: ANY /api/auth/login

`backend/accounts/urls.py` declares `ANY /api/auth/login` 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: ANY /api/auth/me

`backend/accounts/urls.py` declares `ANY /api/auth/me` 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: ANY /api/auth/register

`backend/accounts/urls.py` declares `ANY /api/auth/register` 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: ANY /api/bank/

`backend/config/urls.py` declares `ANY /api/bank/` 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: ANY /api/bank/ingest/

`backend/bank/urls.py` declares `ANY /api/bank/ingest/` 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: ANY /api/bank/ingest/<int:job_id>/

`backend/bank/urls.py` declares `ANY /api/bank/ingest/<int:job_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: ANY /api/corpus/

`backend/config/urls.py` declares `ANY /api/corpus/` 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: ANY /api/corpus/documents/<int:document_id>/chapter-map/

`backend/corpus/urls.py` declares `ANY /api/corpus/documents/<int:document_id>/chapter-map/` 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 wh…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/corpus/documents/<int:document_id>/chapter-map/nodes/<str:stable_node_id>/

`backend/corpus/urls.py` declares `ANY /api/corpus/documents/<int:document_id>/chapter-map/nodes/<str:stable_node_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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/papers/

`backend/config/urls.py` declares `ANY /api/papers/` 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: ANY /api/papers/<int:pk>/

`backend/papers/urls.py` declares `ANY /api/papers/<int:pk>/` 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: ANY /api/papers/<int:pk>/answer-key/pdf/

`backend/papers/urls.py` declares `ANY /api/papers/<int:pk>/answer-key/pdf/` 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: ANY /api/papers/<int:pk>/approve/

`backend/papers/urls.py` declares `ANY /api/papers/<int:pk>/approve/` 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: ANY /api/papers/<int:pk>/pdf/

`backend/papers/urls.py` declares `ANY /api/papers/<int:pk>/pdf/` 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: frontend/src/mocks/paper-document-v1.mock.ts (1802 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/46e5b48d-4f5f-49d8-adcf-ca372dceccf9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/46e5b48d-4f5f-49d8-adcf-ca372dceccf9/

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.