ahmed921x-art/bsc-ku — Repobility public scan

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

ahmed921x-art/bsc-ku

https://github.com/ahmed921x-art/bsc-ku · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

36 raw signals (0 security + 36 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -7.6 (diff) · 33 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

Security checks

55.6% cov · 33 findings

click to filter

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 12 High 0 Medium 16 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 33 Crowd 0 Layer: Frontend 2 Security 24 Quality 7

Exclude dismissed / FP Exclude test files

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 69.1/100 with 55.6% coverage. It contains 58 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 36 findings — concentrated in security (27), quality (7), frontend (2). Risk profile is high: 15 critical, 0 high, 16 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 32 of 33 actionable findings. 36 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.

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in about.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

lines 526, 555

about.html:526, 555 (2 hits)

critical System graph security Secrets conf 1.00 Possible secret in admin.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

admin.html:1127

critical System graph security Secrets conf 1.00 Possible secret in advisors.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

advisors.html:421

critical System graph security Secrets conf 1.00 Possible secret in ask.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

ask.html:428

critical System graph security Secrets conf 1.00 Possible secret in events.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

events.html:443

critical System graph security Secrets conf 1.00 Possible secret in index.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

index.html:916

critical System graph security Secrets conf 1.00 Possible secret in major.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

major.html:567

critical System graph security Secrets conf 1.00 Possible secret in notes.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

notes.html:627

critical System graph security Secrets conf 1.00 Possible secret in seed-team.js

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

seed-team.js:19

critical System graph security Secrets conf 1.00 3 occurrences Possible secret in services.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

lines 733, 845, 856

services.html:733, 845, 856 (3 hits)

critical System graph security Secrets conf 1.00 Possible secret in team.html

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

team.html:435

critical System graph security Secrets conf 1.00 Possible secret in urgent-ann.js

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

urgent-ann.js:4

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — gemini-worker.js:40

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 Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci, tests, operator-readme. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

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 'direct_innerhtml_assignment' in about.html:609

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

about.html:609 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in admin.html:1179

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

admin.html:1179 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in advisors.html:439

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

advisors.html:439 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in ask.html:569

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

ask.html:569 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in events.html:450

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

events.html:450 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:948

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

index.html:948 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in major.html:615

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

major.html:615 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in notes.html:762

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

notes.html:762 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in services.html:744

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

services.html:744 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in team.html:455

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

team.html:455 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in theme.js:46

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

theme.js:46 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in urgent-ann.js:21

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

urgent-ann.js:21 Direct innerhtml assignment

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 9 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — urgent-ann.js:24

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

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 quality Docs conf 1.00 No README detected

No README file was found. Generated repos without README context are hard to operate, validate, or safely hand off.

ReadmeRepo hardeningGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — seed-team.js:64

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

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/95930479-ad19-4992-aad9-9628f40b18e4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/95930479-ad19-4992-aad9-9628f40b18e4/

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.