smith-horn/skillsmith

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.

68 of your 211 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 7.18s · analysis 78.79s · 20.3 MB · GitHub API rate-limit (preflight)

https://github.com/smith-horn/skillsmith · scanned 2026-06-06 00:04 UTC (4 days, 3 hours ago) · 10 languages

1245 raw signals (183 security + 1062 graph) 39th percentile · Typescript · large (100-500K LoC) System graph score 65 (higher by 8)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 3 hours ago · v2 · 617 actionable findings from 2 signal sources. 96 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 · 523 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	42.7	0.25	10.68
`testing_score`	100.0	0.20	20.00
`documentation_score`	98.1	0.15	14.71
`practices_score`	83.0	0.15	12.45
`code_quality`	58.8	0.10	5.88
Overall		1.00	72.7

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 6 High 78 Medium 54 Low 293 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 94 System graph 523 Crowd 0 Layer: Quality 228 Security 13 Software 101 Cicd 5 Frontend 210 Network 3 Hardware 2 Api 55

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.

Legacy markers 8 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.

8 matching findings on this repo

low Old/deprecated-named symbol `085_new_legacy` in scripts/tests/audit-standards-m…
low Old/deprecated-named symbol `getLicenseStatusLegacy` in packages/cli/tests/lice…
low Old/deprecated-named symbol `pasteLegacy` in packages/cli/src/commands/login.ts…
low Old/deprecated-named symbol `hasPasteLegacy` in packages/cli/src/commands/login…
low Old/deprecated-named symbol `getLicenseStatusLegacy` in packages/cli/src/utils/…
low Old/deprecated-named symbol `getLicenseStatusLegacy` in packages/cli/src/utils/…
low Old/deprecated-named symbol `getLicenseStatusLegacy` in packages/cli/src/utils/…
low Old/deprecated-named symbol `sk_live_legacy` in packages/core/src/config/token-…

View all legacy markers findings →

Commented-out code 155 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 (8 lines) in vitest.config.colocated.ts:1
info Commented-code block (6 lines) in vitest.e2e.config.ts:37
info Commented-code block (5 lines) in vitest.config.root-tests.ts:1
info Commented-code block (6 lines) in lint-staged.config.js:40
info Commented-code block (7 lines) in eslint.config.js:35
info Commented-code block (5 lines) in vitest.config.ts:24
info Commented-code block (6 lines) in tests/e2e/checkout-flow.spec.ts:249
info Commented-code block (5 lines) in tests/e2e/mcp/usage-counter.e2e.test.ts:105
info Commented-code block (6 lines) in tests/e2e/cli/usage-counter.e2e.test.ts:54
info Commented-code block (5 lines) in tests/e2e/website/account-usage.e2e.test.ts:87
info Commented-code block (14 lines) in apps/api-proxy/api/proxy.ts:33
info Commented-code block (6 lines) in scripts/session-priming-query.ts:39

View all commented-out code findings →

Config drift 17 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.

12 matching findings on this repo

low File has no detected symbols: vitest.config.colocated.ts
low File has no detected symbols: vitest.e2e.config.ts
low File has no detected symbols: vitest-e2e.config.ts
low File has no detected symbols: lint-staged.config.js
low File has no detected symbols: eslint.config.js
low File has no detected symbols: vitest.config.ts
low File has no detected symbols: packages/enterprise/vitest.config.ts
low Stray `console.log` in TS/JS — packages/cli/src/commands/config.ts:159
info Commented-code block (8 lines) in vitest.config.colocated.ts:1
info Commented-code block (6 lines) in vitest.e2e.config.ts:37
info Commented-code block (5 lines) in vitest.config.root-tests.ts:1
info Commented-code block (6 lines) in lint-staged.config.js:40

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/72a3ffa5-cbcd-4a9e-8c7c-015f5f1e3595/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/72a3ffa5-cbcd-4a9e-8c7c-015f5f1e3595/

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.