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.

rotifer-protocol/rotifer-playground

https://github.com/rotifer-protocol/rotifer-playground · scanned 2026-06-15 23:56 UTC (2 months, 3 weeks ago)

142 raw signals (0 security + 142 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 140 actionable findings from 1 signal source. 2 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 · 140 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 11 Medium 41 Low 72 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 140 Crowd 0 Layer: Software 4 Api 1 Frontend 64 Security 25 Cicd 2 Quality 44

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

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.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `isDbLegacy` in src/utils/phenotype-validator.ts:243

View all legacy markers findings →

Commented-out code 11 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/`.

11 matching findings on this repo

info Commented-code block (5 lines) in tests/fixtures/polyglot/build-fixtures.mjs:59
info Commented-code block (5 lines) in tests/fixtures/polyglot/as-style/source/index…
info Commented-code block (6 lines) in tests/e2e/network.test.ts:30
info Commented-code block (6 lines) in tests/e2e/seasons-rpc.test.ts:6
info Commented-code block (6 lines) in tests/e2e/polyglot-byo-wasm.test.ts:3
info Commented-code block (5 lines) in tests/e2e/network-v09.test.ts:9
info Commented-code block (5 lines) in scripts/post-deploy-smoke-test.ts:54
info Commented-code block (5 lines) in src/types/phenotype.ts:268
info Commented-code block (6 lines) in src/commands/versions.ts:13
info Commented-code block (5 lines) in src/commands/whoami.ts:9
info Commented-code block (5 lines) in src/utils/javy-compiler.ts:37

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

high Agent instruction/config may expose a secret: genes/debugger/SKILL.md genes/debugger/SKILL.md:211
high Agent instruction/config may expose a secret: genes/docs-writer/SKILL.md genes/docs-writer/SKILL.md:332
high Agent instruction/config may expose a secret: genes/devops-automator/SKILL.md genes/devops-automator/SKILL.md:108
high Agent instruction/config may expose a secret: genes/api-designer/SKILL.md genes/api-designer/SKILL.md:318
high Agent instruction/config may expose a secret: genes/security-auditor/SKILL.md genes/security-auditor/SKILL.md:367

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/7620dfa8-c942-4fdc-8a0b-1790ab2c1771/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7620dfa8-c942-4fdc-8a0b-1790ab2c1771/

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.