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.
Sign up free Scan another repo

VeelaCleave/brikie

https://github.com/VeelaCleave/brikie · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

47 raw signals (0 security + 47 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
76.5
/100
Security checks
77
0 findings
System graph
77
88.9% cov · 35 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 0 Medium 4 Low 22 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 35 Crowd 0 Layer: Software 9 Hardware 2 Frontend 1 Cicd 1 Quality 21 Security 1
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 76.5/100 with 88.9% coverage. It contains 2823 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 47 findings — concentrated in quality (33), software (9), hardware (2). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 26 of 35 actionable findings. 47 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: AGENTS.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
AGENTS.md:26 Supply chainAgents md
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/docker.yml CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — brikie/gateway.py:98
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 72 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:13 containersPinned dependencies
low System graph quality Integrity conf 1.00 8 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: brikie/bricks/interface/telegram.py:name, brikie/bricks/interface/cli.py:name This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
8 occurrences
repo-level (8 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: brikie/bricks/security/firewall.py:evaluate, brikie/bricks/security/sandbox.py:evaluate, brikie/bricks/security/base.py:evaluate This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consol…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: brikie/bricks/memory/mempalace/mempalace_store.py:initialize, brikie/bricks/memory/lcm/lcm_store.py:initialize, brikie/bricks/tool/swarm/swarm_store.py:initialize, brikie/bricks/tool/goals/goal_store.py:initialize This is *the* AI-coder failure mode …
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 7 places
Functions with the same first-5-line body hash: brikie/bricks/security/base.py:name, brikie/bricks/provider/base.py:name, brikie/bricks/interface/base.py:name, brikie/bricks/improvement/base.py:name This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_migrate_v1_to_v2` in brikie/bricks/memory/sqlite_pool.py:39
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_installed_returns_copy` in tests/test_registry.py:156
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_snapshot_returns_deep_copy` in tests/test_kernel.py:116
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: add_command_tool
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/bricks/security/firewall.py:153
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/auth/openai_oauth.py:332
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/server/registry_server.py:71
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/server/registry_server.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: expand
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/bricks/memory/lcm/lcm_store.py:235
low System graph software Dead code conf 1.00 Possibly dead Python function: find_manifest_by_uri
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/bricks/tool/source_audit_store.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/auth/openai_oauth.py:347
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/server/registry_server.py:199
low System graph software Dead code conf 1.00 Possibly dead Python function: unregister_soul
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
brikie/bricks/interface/event_bus.py:62
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph quality Complexity conf 1.00 Very large file: brikie/bricks/tool/swarm/swarm_brick.py (1141 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: brikie/kernel/event_loop.py (1614 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/3a61a4d1-4490-468f-805a-aff7b35fe564/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3a61a4d1-4490-468f-805a-aff7b35fe564/

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.