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.

tam159/next-role

https://github.com/tam159/next-role · scanned 2026-06-16 00:29 UTC (2 months, 2 weeks ago)

43 raw signals (0 security + 43 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 37 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 14 Low 10 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 37 Crowd 0 Layer: Frontend 9 Hardware 5 Security 3 Cicd 2 Quality 18

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 57.5/100 with 88.9% coverage. It contains 548 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 43 findings — concentrated in quality (19), frontend (9), cicd (7). Risk profile is low: 0 critical, 0 high, 16 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 24 of 37 actionable findings. 43 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.

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/app/components/FileViewDialog.tsx:376

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 frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/app/print/file/page.tsx:149

Fq dangerous html

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/app/lib/agentFiles.ts:271

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/settings.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/settings.json VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/app/career_agent/AGENTS.md

backend/app/career_agent/AGENTS.md VerificationAgents md

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/app/career_agent/skills/hiring-recon/hiring-recon/SKILL.md

backend/app/career_agent/skills/hiring-recon/hiring-recon/SKILL.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: backend/app/career_agent/skills/interview-coach/interview-coach/SKILL.md

backend/app/career_agent/skills/interview-coach/interview-coach/SKILL.md VerificationSkill file

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 cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned

astral-sh/[email protected] can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 31, 40, 79

.github/workflows/ci.yml:31, 40, 79 (3 hits)

CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/app/components/FileViewDialog.tsx:376

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

frontend/src/app/components/FileViewDialog.tsx:376 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/app/print/file/page.tsx:149

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

frontend/src/app/print/file/page.tsx:149 Dangerous innerhtml

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 15 placeholder/mock markers across 8 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 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: langchain/langgraph-api:3.13

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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:24-alpine

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 cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 26, 45, 56, 76

.github/workflows/ci.yml:26, 45, 56, 76 (4 hits)

CI/CD securitySupply chainGithub actions

low System graph quality Tests conf 1.00 Low test-to-source ratio

7 tests / 66 src (ratio 0.11).

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/app/career_agent/middleware.py:wrap_model_call, backend/app/career_agent/middleware.py:wrap_model_call This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document …

2 occurrences

repo-level (2 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in backend/app/career_agent/middleware.py:146

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 `model_copy` in backend/tests/career_agent/test_middleware_model_override.py:10

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 `page_3_image_23_v2` in backend/tests/career_agent/test_tools.py:289

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 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

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/9f259ff4-6759-4df8-8963-9e98f024f175/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9f259ff4-6759-4df8-8963-9e98f024f175/

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.