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.

Tobillicious/te-kete-ako-production

https://github.com/Tobillicious/te-kete-ako-production · scanned 2026-06-16 00:41 UTC (2 months, 1 week ago)

888 raw signals (0 security + 888 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 858 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 53 Medium 393 Low 359 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 858 Crowd 0 Layer: Software 26 Frontend 202 Hardware 11 Security 333 Cicd 3 Quality 225 Api 58

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 4 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 8 places
low Near-duplicate function bodies in 5 places

View all duplicates & near-duplicates findings →

Legacy markers 49 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

12 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/legacy/scan_public.js:21
low Stray `console.log` in TS/JS — scripts/legacy/generate_inventory.js:36
low Stray `console.log` in TS/JS — scripts/legacy/check_links.js:60
low Stray `console.log` in TS/JS — scripts/legacy/load-env-keys.js:4
low Stray `console.log` in TS/JS — scripts/legacy/analyze_sitemap.js:72
low Stray `console.log` in TS/JS — mcp-server/server.legacy.js:76
medium Insecure pattern 'direct_innerhtml_assignment' in units/_legacy_archive/hamilto… units/_legacy_archive/hamilton-zoo-grid-explorer-…:406
medium Insecure pattern 'direct_innerhtml_assignment' in units/_legacy_archive/lessons… units/_legacy_archive/lessons/unit-5-lesson-4.html:548
medium Insecure pattern 'direct_innerhtml_assignment' in units/_legacy_archive/lessons… units/_legacy_archive/lessons/unit-4-lesson-3.html:420
medium Insecure pattern 'direct_innerhtml_assignment' in units/_legacy_archive/lessons… units/_legacy_archive/lessons/unit-5-lesson-3.html:479
medium Insecure pattern 'direct_innerhtml_assignment' in units/_legacy_archive/lessons… units/_legacy_archive/lessons/unit-5-lesson-2.html:408
medium Insecure pattern 'direct_innerhtml_assignment' in units/_legacy_archive/aotearo… units/_legacy_archive/aotearoas-living-landscapes…:404

View all legacy markers findings →

Commented-out code 42 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (7 lines) in sw.js:143
info Commented-code block (5 lines) in docker/te-mahara/worker.py:78
info Commented-code block (6 lines) in docker/te-aronui/test_rlm_e2e.py:254
info Commented-code block (5 lines) in docker/te-aronui/test_async_rlm.py:46
info Commented-code block (5 lines) in docker/te-aronui/test_overlap.py:16
info Commented-code block (5 lines) in tests/playwright/auth-oauth.spec.ts:163
info Commented-code block (5 lines) in tests/playwright/student-portal.spec.ts:58
info Commented-code block (5 lines) in tests/playwright/auth-gates.spec.ts:31
info Commented-code block (5 lines) in _personal/sovereign-lattice/content/tools/win…
info Commented-code block (6 lines) in js/site-gate.js:63
info Commented-code block (5 lines) in js/workshop-core.js:171
info Commented-code block (5 lines) in js/quantum-adaptive-engine.js:673

View all commented-out code findings →

Config drift 5 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

5 matching findings on this repo

low Stray `console.log` in TS/JS — scripts/generate-env-config.js:71
medium Runtime service client appears to use placeholder configuration
low Old/deprecated-named symbol `eleven_multilingual_v2` in js/pronunciation-config…
medium `fetch()` without try/.catch or AbortSignal — js/pronunciation-config.js:317
high Dangling fetch: GET /api/youtube-config (js/youtube-api.js:50)

View all config drift findings →

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/e6ea8d64-589f-48cd-99a8-11aae434eda0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e6ea8d64-589f-48cd-99a8-11aae434eda0/

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.