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.

chpark1358/chemical_search

https://github.com/chpark1358/chemical_search · scanned 2026-06-17 01:47 UTC (1 month, 1 week ago)

28 raw signals (0 security + 28 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 27 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 6 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 27 Crowd 0 Layer: Frontend 7 Data 1 Hardware 2 Quality 14 Security 3

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

Showing 16 of 27 actionable findings. 28 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 auth conf 1.00 FastAPI POST `create_search` without auth dependency — scripts/chemical_search/api.py:443

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

scripts/chemical_search/api.py:443 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `normalize` without auth dependency — scripts/chemical_search/api.py:422

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

scripts/chemical_search/api.py:422 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `select_candidate` without auth dependency — scripts/chemical_search/api.py:454

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

scripts/chemical_search/api.py:454 securityAuth fastapi unauth mutation

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — src/lib/text.ts:8

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 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. 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph data Coverage conf 1.00 ORM models found but no DB engine detected

The repo defines tables/models but no DB connection string was found. Likely lives in env vars or a config file the scanner didn't read.

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 24 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

low System graph quality Integrity conf 1.00 5 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `CI`, `EPO_OPS_CONSUMER_KEY`, `EPO_OPS_CONSUMER_SECRET`, `NEXT_DIST_DIR`, `PLAYWRIGHT_BASE_URL`. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 7 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.11-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:7 containersPinned dependencies

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

13 tests / 68 src (ratio 0.19).

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: scripts/chemical_search/http_client.py:get_json, scripts/chemical_search/http_client.py:get_text 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 se…

duplicatesduplication

low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: scripts/chemical_search/providers.py:search_papers, scripts/chemical_search/providers.py:search_papers, scripts/chemical_search/providers.py:search_papers This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.h…

2 occurrences

repo-level (2 hits)

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

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/8db2c1ee-347a-4324-954c-10db6091d07d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/8db2c1ee-347a-4324-954c-10db6091d07d/

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.