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

transnavi/transnavi.jp

https://github.com/transnavi/transnavi.jp · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

41 raw signals (5 security + 36 graph)

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

Complete repo analysis

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

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

Showing 21 of 39 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.

high Security checks quality Testing conf 0.78 3 occurrences Foundry mined test ci gap after feedback: transnavi/transnavi.jp
Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…
3 occurrences
repo-level (3 hits)
medium Security checks quality Practices conf 0.62 Foundry mined assumption checks: transnavi/transnavi.jp
Comment chain pattern product: assumption_checks Repo: transnavi/transnavi.jp Thread: transnavi/transnavi.jp#1 Outcome: ambiguous_needs_more_evidence Thread label: thread_has_human_issue_and_fix_context Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_ar…
medium Security checks quality maintenance conf 0.70 3 occurrences Foundry mined blueprint gap alignment: transnavi/transnavi.jp
Graph query export: Human feedback aligned with blueprint or architecture gaps Query id: blueprint_gap_alignment Query type: motif_query Intent: Curriculum-gap examples connecting issue threads to helicopter-view gaps. Motif: blueprint_gap_alignment Training usage: curriculum_gap Graph gold label: …
3 occurrences
repo-level (3 hits)
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — scripts/fetch-wikidata-sitelinks.mjs:28
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 — scripts/fetch-wikidata-translations.mjs:18
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 — scripts/fetch-work-posters.mjs:27
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 — scripts/geocode-pois.mjs:28
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 — src/worker.ts:6
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 security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/citations.js:18
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/citations.js:18 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/filter-index.js:224
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/filter-index.js:224 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/page-toc.js:79
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/page-toc.js:79 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in public/search.js:178
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
public/search.js:178 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in scripts/gen-page-dates.mjs:4
Found a known-risky pattern (node_child_process). Review and replace if possible.
scripts/gen-page-dates.mjs:4 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 Tests conf 1.00 Very low test-to-source ratio
4 test file(s) for 47 source file(s) (ratio 0.09). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 53 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 Integrity conf 1.00 Old/deprecated-named symbol `isLegacy` in scripts/analyze-links.mjs:105
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 `rest_v1` in scripts/fetch-work-posters.mjs:50
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
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — scripts/audit-clinic-tags.ts:84
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
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/55299e7f-5cc9-4fd2-af25-3e48660ed99c/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/55299e7f-5cc9-4fd2-af25-3e48660ed99c/

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.