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

dkedar7/langstage-jupyter

https://github.com/dkedar7/langstage-jupyter · scanned 2026-06-17 01:57 UTC (1 month, 1 week ago)

25 raw signals (0 security + 25 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ +6.7 (diff) · 18 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
83.4
/100
Security checks
83
0 findings
System graph
83
55.6% cov · 18 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 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 18 Crowd 0 Layer: Software 6 Frontend 4 Security 1 Cicd 2 Quality 5
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 83.4/100 with 55.6% coverage. It contains 213 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 25 findings — concentrated in cicd (9), software (6), quality (5). Risk profile is low: 0 critical, 0 high, 4 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 15 of 18 actionable findings. 25 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 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 quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — langstage_jupyter/agent.py:112
`requests.get(...)` 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
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 49 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 cicd CI/CD security conf 1.00 8 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 8 locations
.github/workflows/ui-tests.yml:17, 20, 25, 63, 72 (5 hits)
.github/workflows/test.yml:21, 24, 30 (3 hits)
CI/CD securitySupply chainGithub actions
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: langstage_jupyter/handlers.py:post, langstage_jupyter/handlers.py:post, langstage_jupyter/handlers.py:post, langstage_jupyter/handlers.py:post This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hy…
duplicatesduplication
low System graph software Dead code conf 1.00 Possibly dead Python function: create_notebook
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
langstage_jupyter/agent.py:204
low System graph software Dead code conf 1.00 Possibly dead Python function: execute_cell
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
langstage_jupyter/agent.py:348
low System graph software Dead code conf 1.00 Possibly dead Python function: insert_code_cell
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
langstage_jupyter/agent.py:226
low System graph software Dead code conf 1.00 Possibly dead Python function: modify_cell
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
langstage_jupyter/agent.py:282
low System graph software Dead code conf 1.00 Possibly dead Python function: run_agent_resume
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
langstage_jupyter/handlers.py:195
low System graph software Dead code conf 1.00 Possibly dead Python function: run_agent_stream
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
langstage_jupyter/handlers.py:83
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/handler.ts:36
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
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/index.ts:37
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
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/widget.tsx:265
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/820d3c9e-3f79-476e-96a3-ca5b851a7c1f/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/820d3c9e-3f79-476e-96a3-ca5b851a7c1f/

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.