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.

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 206.54s for a 211.7 MB repo slow.
Repobility's analysis ran in 8.26s after the clone landed.

crewAIInc/crewAI

https://github.com/crewAIInc/crewAI · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago) · 10 languages

443 raw signals (150 security + 293 graph) 11/13 scanners ran 36th percentile · Python · large (100-500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v3 · 312 actionable findings from 2 signal sources. 106 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 · 265 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	85.0	0.15	12.75
`security_score`	100.0	0.25	25.00
`testing_score`	100.0	0.20	20.00
`documentation_score`	82.0	0.15	12.30
`practices_score`	91.0	0.15	13.65
`code_quality`	55.0	0.10	5.50
Overall		1.00	89.2

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 7 High 4 Medium 136 Low 104 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 47 System graph 265 Crowd 0 Layer: Quality 167 Security 9 Software 23 Cicd 2 Frontend 1 Network 110

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

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 5 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 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 `_use_legacy` in lib/crewai/src/crewai/rag/embeddin…

View all legacy markers findings →

Commented-out code 23 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 conftest.py:77
info Commented-code block (5 lines) in lib/crewai/tests/test_flow_conversation.py:41
info Commented-code block (6 lines) in lib/crewai/tests/events/test_llm_finish_reaso…
info Commented-code block (5 lines) in lib/crewai/src/crewai/memory/types.py:12
info Commented-code block (5 lines) in lib/crewai/src/crewai/memory/encoding_flow.py…
info Commented-code block (6 lines) in lib/crewai/src/crewai/memory/unified_memory.p…
info Commented-code block (5 lines) in lib/crewai/src/crewai/agents/step_executor.py…
info Commented-code block (5 lines) in lib/crewai/src/crewai/rag/factory.py:15
info Commented-code block (11 lines) in lib/crewai/src/crewai/flow/visualization/ass…
info Commented-code block (6 lines) in lib/crewai/src/crewai/flow/runtime/__init__.p…
info Commented-code block (6 lines) in lib/crewai/src/crewai/tools/agent_tools/base_…
info Commented-code block (5 lines) in lib/crewai/src/crewai/experimental/agent_exec…

View all commented-out code findings →

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

3 matching findings on this repo

high [MINED131] pre-commit hook `https://github.com/astral-sh/uv-pre-commit` pinned … .pre-commit-config.yaml:23
low Old/deprecated-named symbol `model_copy` in lib/crewai/src/crewai/state/checkpo…
low Stub function `configure_logging` (body is just `pass`/`return`) — lib/crewai-t…

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/79a38bd6-8ae7-4ba7-866b-4c4ca1eeb85e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/79a38bd6-8ae7-4ba7-866b-4c4ca1eeb85e/

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.