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.

terrene-foundation/kailash-coc-rs

https://github.com/terrene-foundation/kailash-coc-rs · scanned 2026-06-16 00:32 UTC (2 months, 2 weeks ago)

604 raw signals (0 security + 604 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 593 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 138 Medium 344 Low 38 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 593 Crowd 0 Layer: Software 1 Frontend 29 Network 4 Hardware 3 Security 195 Cicd 3 Quality 358

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.

Commented-out code 68 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 (5 lines) in .claude/audit-fixtures/proximity-band-budget/…
info Commented-code block (6 lines) in .claude/audit-fixtures/scan-synced-disclosure…
info Commented-code block (6 lines) in .claude/audit-fixtures/validate-emit/run.mjs:…
info Commented-code block (5 lines) in .claude/audit-fixtures/codex-dispatcher/run.m…
info Commented-code block (5 lines) in .claude/audit-fixtures/validate-proximity-ban…
info Commented-code block (6 lines) in .claude/audit-fixtures/variant-overlay/run.mj…
info Commented-code block (5 lines) in .claude/audit-fixtures/validate-xref-integrit…
info Commented-code block (5 lines) in .claude/audit-fixtures/forest-ledger/run.mjs:…
info Commented-code block (6 lines) in .claude/audit-fixtures/validate-extraction-hi…
info Commented-code block (8 lines) in .claude/audit-fixtures/strip-build-internal/r…
info Commented-code block (5 lines) in .claude/fixtures/validator-13/shape-c-mcp-ret…
info Commented-code block (5 lines) in .claude/fixtures/validator-13/shape-b-two-lay…

View all commented-out code findings →

Config drift 133 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

high Agent instruction/config may expose a secret: GEMINI.md GEMINI.md:663
high Agent instruction/config may expose a secret: AGENTS.md AGENTS.md:649
high Agent instruction/config may expose a secret: .claude/sync-manifest.yaml .claude/sync-manifest.yaml:476
high Agent instruction/config may expose a secret: .claude/rules/env-models.md .claude/rules/env-models.md:49
high Agent instruction/config may expose a secret: .claude/rules/security.md .claude/rules/security.md:23
high Agent instruction/config may expose a secret: .claude/rules/observability.md .claude/rules/observability.md:183
high Agent instruction/config may expose a secret: .claude/rules/llm-auth-strategy-h… .claude/rules/llm-auth-strategy-hygiene.md:25
high Agent instruction/config may expose a secret: .claude/rules/testing.md .claude/rules/testing.md:126
high Agent instruction/config may expose a secret: .claude/agents/codex-architect.md .claude/agents/codex-architect.md:43
high Agent instruction/config may expose a secret: .claude/agents/frameworks/align-s… .claude/agents/frameworks/align-specialist.md:147
high Agent instruction/config may expose a secret: .claude/skills/01-core-sdk/custom… .claude/skills/01-core-sdk/custom-node-guide.md:298
high Agent instruction/config may expose a secret: .claude/skills/01-core-sdk/enterp… .claude/skills/01-core-sdk/enterprise-infrastruct…:15

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/18a26df0-3d3b-4974-bb55-d8a9edbcae3d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/18a26df0-3d3b-4974-bb55-d8a9edbcae3d/

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.