remorses/holocron

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.

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

Scan timing: clone 24.26s · analysis 3.23s · 28.5 MB · GitHub API rate-limit (preflight)

https://github.com/remorses/holocron · scanned 2026-06-05 21:32 UTC (4 days, 12 hours ago) · 10 languages

368 raw signals (48 security + 320 graph) 11/13 scanners ran 78th percentile · Typescript · medium (20-100K LoC) System graph score 75 (higher by 6)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 12 hours ago · v2 · 186 actionable findings from 2 signal sources. 22 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 · 160 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	95.0	0.20	19.00
`documentation_score`	70.0	0.15	10.50
`practices_score`	67.0	0.15	10.05
`code_quality`	70.0	0.10	7.00
Overall		1.00	80.5

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 4 Medium 31 Low 84 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 26 System graph 160 Crowd 0 Layer: Quality 86 Software 53 Security 9 Cicd 2 Api 1 Frontend 35

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

2 matching findings on this repo

low Old/deprecated-named symbol `certIssuerDNLegacy` in og-worker/worker-configurat…
low Old/deprecated-named symbol `certIssuerDNLegacy` in website/worker-configuratio…

View all legacy markers findings →

Commented-out code 40 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 og-worker/worker-configuration.d.ts:12023
info Commented-code block (5 lines) in integration-tests/e2e/basic/basic.test.ts:390
info Commented-code block (5 lines) in integration-tests/e2e/openapi/openapi.test.ts…
info Commented-code block (6 lines) in website/worker-configuration.d.ts:9983
info Commented-code block (5 lines) in website/vitest.config.ts:14
info Commented-code block (5 lines) in website/scripts/generate-openapi.ts:5
info Commented-code block (5 lines) in website/src/deploy-api.ts:120
info Commented-code block (5 lines) in website/src/api.ts:33
info Commented-code block (5 lines) in website/src/usage-counter-do.ts:1
info Commented-code block (8 lines) in website/src/dashboard.tsx:7
info Commented-code block (5 lines) in website/src/config-override-do.ts:3
info Commented-code block (5 lines) in website/src/api-auth.test.ts:10

View all commented-out code findings →

Config drift 28 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: integration-tests/vite.config.ts
low File has no detected symbols: integration-tests/playwright.deploy-preview.confi…
low File has no detected symbols: integration-tests/fixtures/tailwind-scan/vite.con…
low File has no detected symbols: integration-tests/fixtures/base-path/vite.config.…
low File has no detected symbols: integration-tests/fixtures/changelog/vite.config.…
low File has no detected symbols: integration-tests/fixtures/docs-subfolder/vite.co…
low File has no detected symbols: integration-tests/fixtures/custom-entry/vite.conf…
low File has no detected symbols: integration-tests/fixtures/openapi-pagesdir/vite.…
low File has no detected symbols: cli/src/config.test.ts
low File has no detected symbols: website/vite.config.ts
low File has no detected symbols: website/vitest.config.ts
low File has no detected symbols: website/src/config-override-api.ts

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/0db3f4e2-f899-4f69-a8bd-7fdf1e9b1bf5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/0db3f4e2-f899-4f69-a8bd-7fdf1e9b1bf5/

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.