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-py

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

1425 raw signals (0 security + 1425 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 9 High 81 Medium 241 Low 451 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 1334 Crowd 0 Layer: Software 15 Frontend 36 Hardware 8 Security 139 Cicd 3 Quality 1084 Api 49

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

5 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Legacy markers 21 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 Old/deprecated-named symbol `task_legacy` in tests/integration/test_sql_task_qu…
low Old/deprecated-named symbol `_compute_hash_legacy` in tests/trust/pact/unit/tes…
low Old/deprecated-named symbol `test_from_legacy` in tests/trust/plane/integration…
low Old/deprecated-named symbol `from_legacy` in tests/regression/test_issue_959_tr…
low Old/deprecated-named symbol `extract_legacy` in tests/e2e/test_production_datab…
low Old/deprecated-named symbol `test_canonical_takes_precedence_over_legacy` in pa…
low Old/deprecated-named symbol `test_selector_tier_beats_legacy` in packages/kaila…
low Old/deprecated-named symbol `test_selector_tier_wins_over_legacy` in packages/k…
low Old/deprecated-named symbol `test_backend_canonical_wins_over_legacy` in packag…
low Old/deprecated-named symbol `kaizen_legacy` in packages/kailash-kaizen/tests/e2…
low Old/deprecated-named symbol `_build_from_legacy` in packages/kailash-kaizen/src…
low Old/deprecated-named symbol `test_legacy` in packages/kailash-dataflow/tests/e2…

View all legacy markers findings →

Commented-out code 548 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 tests/conftest.py:44
info Commented-code block (5 lines) in tests/integration/test_durable_execution_engi…
info Commented-code block (12 lines) in tests/integration/test_sql_task_queue_dispat…
info Commented-code block (6 lines) in tests/integration/test_checkpoint_store_redac…
info Commented-code block (8 lines) in tests/integration/test_eatp12_vault_backup_re…
info Commented-code block (6 lines) in tests/integration/test_eatp12_vault_clearance…
info Commented-code block (5 lines) in tests/integration/test_local_runtime_checkpoi…
info Commented-code block (7 lines) in tests/integration/edge/test_edge_integration.…
info Commented-code block (9 lines) in tests/integration/middleware/test_api_gateway…
info Commented-code block (6 lines) in tests/integration/kaizen/test_signature_from_…
info Commented-code block (6 lines) in tests/integration/delegate/test_conformance_v…
info Commented-code block (6 lines) in tests/integration/delegate/conftest.py:60

View all commented-out code findings →

Config drift 79 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 Insecure pattern 'eval_used' in .pre-commit-config.yaml:71 .pre-commit-config.yaml:71
low Insecure pattern 'debug_true' in packages/kailash-kaizen/scripts/demo_alternati… packages/kailash-kaizen/scripts/demo_alternative_…:30
low Insecure pattern 'debug_true' in packages/kailash-kaizen/src/kaizen/core/config… packages/kailash-kaizen/src/kaizen/core/config.py:546
high Insecure pattern 'eval_used' in src/kailash/workflow/cycle_config.py:270 src/kailash/workflow/cycle_config.py:270
high Insecure pattern 'exec_used' in src/kailash/workflow/cycle_config.py:269 src/kailash/workflow/cycle_config.py:269
low Very large file: src/kailash/trust/pact/config.py (1534 lines)
high Agent instruction/config may expose a secret: .claude/rules/security.md .claude/rules/security.md:21
high Agent instruction/config may expose a secret: .claude/rules/testing.md .claude/rules/testing.md:112
high Agent instruction/config may expose a secret: .claude/agents/codex-architect.md .claude/agents/codex-architect.md:36
high Agent instruction/config may expose a secret: .claude/agents/frameworks/infrast… .claude/agents/frameworks/infrastructure-speciali…:143
high Agent instruction/config may expose a secret: .claude/skills/01-core-sdk/produc… .claude/skills/01-core-sdk/production-readiness-p…:50
high Agent instruction/config may expose a secret: .claude/skills/30-claude-code-pat… .claude/skills/30-claude-code-patterns/parallel-m…:135

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/e27717e3-1f49-4c8a-8e02-7a2fa6b035af/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e27717e3-1f49-4c8a-8e02-7a2fa6b035af/

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.