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

Teclever/AgenticBIDPlus

https://github.com/Teclever/AgenticBIDPlus · scanned 2026-06-16 00:31 UTC (2 months, 2 weeks ago)

87 raw signals (0 security + 87 graph)

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

Complete repo analysis

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

JSON
Combined
59.8
/100
Security checks
60
0 findings
System graph
60
100.0% cov · 80 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 3 Medium 12 Low 58 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 80 Crowd 0 Layer: Software 24 Frontend 1 Security 5 Cicd 1 Quality 24 Api 25
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 59.8/100 with 100.0% coverage. It contains 1253 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 87 findings — concentrated in quality (29), software (26), api (25). Risk profile is high: 0 critical, 3 high, 12 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 73 of 80 actionable findings. 87 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.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: AGENTS.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
AGENTS.md:49 SecretsAgents md
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: frontend/.env.development
`frontend/.env.development` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
frontend/.env.development ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: frontend/.env.production
`frontend/.env.production` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
frontend/.env.production ConfigEnv fileRuntime env
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/app/components/ui/chart.tsx:83
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/public/mockServiceWorker.js:238
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/app/components/ui/chart.tsx:83
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/app/components/ui/chart.tsx:83 Dangerous innerhtml
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bidplus/adapters/gem.py:109
`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
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bidplus/adapters/hal.py:110
`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
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — bidplus/adapters/isro.py:109
`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
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 13 placeholder/mock markers across 9 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
1 test file(s) for 143 source file(s) (ratio 0.01). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 14 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `BIDPLUS_OVERNIGHT_DEADLINE`, `BIDPLUS_RETENTION_DAYS`, `BIDPLUS_RUNTIME_DIR`, `ELIM_DELTA_PROMOTION_THRESHOLD`, `ELIM_DELTA_WEEKLY_DAYS`, `ELIM_HIGH_SUPPORT`, `OUR_VENDOR_ALIASES`, `PASS1_BATCH` + 6 more. Add them (with a placeholder/comment) to .…
config drift
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 308 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 quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence
The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.
Governance
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: hal_portal/src/hal_tool.py:cmd_explain, isro_portal/isro_tool.py:cmd_explain 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.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: bidplus/adapters/gem.py:scoring_records, bidplus/adapters/isro.py:scoring_records, bidplus/adapters/hal.py:scoring_records This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate …
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph software Dead code conf 1.00 Possibly dead Python function: click_search
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
hal_portal/src/modules/session.py:150
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_accept
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:574
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_add
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/users.py:43
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_boost_backfill
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:366
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_edit
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/users.py:58
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_eliminate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:494
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_gate
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:310
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_governance_apply
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:612
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_governance_delta
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:589
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_list
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/users.py:85
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_merge
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:460
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_promote
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:556
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_remove
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/users.py:72
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_run_status
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:434
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_score
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:536
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_singletender_backfill
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:330
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_summarize
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:266
low System graph software Dead code conf 1.00 Possibly dead Python function: cmd_sweep
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/launcher.py:292
low System graph software Dead code conf 1.00 Possibly dead Python function: collision_rows
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
bidplus/eliminator.py:243
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_page
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gem_portal/gem_tool.py:87
low System graph software Dead code conf 1.00 Possibly dead Python function: log_progress
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
isro_portal/modules/logutil.py:48
low System graph software Dead code conf 1.00 Possibly dead Python function: mark_org_complete
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gem_portal/gem_tool.py:342
low System graph software Dead code conf 1.00 3 occurrences Possibly dead Python function: save_batch
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
3 files, 3 locations
gem_portal/gem_tool.py:147
hal_portal/src/hal_tool.py:85
isro_portal/isro_tool.py:324
low System graph software Dead code conf 1.00 Possibly dead Python function: score_bid_pass1
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
gem_portal/modules/scorer_pass1.py:213
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 Integrity conf 1.00 Stub function `load_dotenv` (body is just `pass`/`return`) — isro_portal/isro_tool.py:27
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/activity
`bidplus/web/app.py` declares `GET /api/activity` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/auth/me
`bidplus/web/app.py` declares `GET /api/auth/me` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/generating
`bidplus/web/app.py` declares `GET /api/generating` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/notifications/auto-filtered
`bidplus/web/app.py` declares `GET /api/notifications/auto-filtered` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/notifications/auto-filtered/count
`bidplus/web/app.py` declares `GET /api/notifications/auto-filtered/count` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/portals/{portal}/bids
`bidplus/web/app.py` declares `GET /api/portals/{portal}/bids` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/portals/{portal}/bids/{bidKey:path}
`bidplus/web/app.py` declares `GET /api/portals/{portal}/bids/{bidKey:path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/portals/{portal}/bids/{bidKey:path}/document
`bidplus/web/app.py` declares `GET /api/portals/{portal}/bids/{bidKey:path}/document` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/portals/{portal}/bids/{bidKey:path}/documents
`bidplus/web/app.py` declares `GET /api/portals/{portal}/bids/{bidKey:path}/documents` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/portals/{portal}/bids/{bidKey:path}/documents/download
`bidplus/web/app.py` declares `GET /api/portals/{portal}/bids/{bidKey:path}/documents/download` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/portals/{portal}/stats
`bidplus/web/app.py` declares `GET /api/portals/{portal}/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/scrape-runs
`bidplus/web/app.py` declares `GET /api/scrape-runs` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /api/system-alerts
`bidplus/web/app.py` declares `GET /api/system-alerts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /{full_path:path}
`bidplus/web/app.py` declares `GET /{full_path:path}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/login
`bidplus/web/app.py` declares `POST /api/auth/login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/auth/logout
`bidplus/web/app.py` declares `POST /api/auth/logout` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/notifications/auto-filtered/save-all
`bidplus/web/app.py` declares `POST /api/notifications/auto-filtered/save-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/notifications/auto-filtered/viewed
`bidplus/web/app.py` declares `POST /api/notifications/auto-filtered/viewed` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/notifications/auto-filtered/{portal}/{bidKey:path}/dispute
`bidplus/web/app.py` declares `POST /api/notifications/auto-filtered/{portal}/{bidKey:path}/dispute` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or docume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/portals/{portal}/bids/bulk-disposition
`bidplus/web/app.py` declares `POST /api/portals/{portal}/bids/bulk-disposition` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/portals/{portal}/bids/{bidKey:path}/disposition
`bidplus/web/app.py` declares `POST /api/portals/{portal}/bids/{bidKey:path}/disposition` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/portals/{portal}/bids/{bidKey:path}/documents/fetch
`bidplus/web/app.py` declares `POST /api/portals/{portal}/bids/{bidKey:path}/documents/fetch` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/portals/{portal}/bids/{bidKey:path}/generate-summary
`bidplus/web/app.py` declares `POST /api/portals/{portal}/bids/{bidKey:path}/generate-summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/portals/{portal}/bids/{bidKey:path}/promote
`bidplus/web/app.py` declares `POST /api/portals/{portal}/bids/{bidKey:path}/promote` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /api/system-alerts/retry
`bidplus/web/app.py` declares `POST /api/system-alerts/retry` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
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/3c9d84db-a701-4b1e-853f-7e830ea85895/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3c9d84db-a701-4b1e-853f-7e830ea85895/

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.