Imbad0202/academic-research-skills

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.

https://github.com/Imbad0202/academic-research-skills.git · scanned 2026-05-16 02:10 UTC (2 weeks, 6 days ago) · 10 languages

71 findings (7 legacy + 64 scanner) 85th percentile · Python · medium (20-100K LoC) Scanner says 86 (lower by 5)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 6 days ago · v1 · 6 findings from 1 source. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-17-v4 calibration-aware

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	94.8	0.25	23.70
`testing_score`	100.0	0.20	20.00
`documentation_score`	100.0	0.15	15.00
`practices_score`	65.0	0.15	9.75
`code_quality`	66.2	0.10	6.62
Overall		1.00	81.1

Calibrated penalty buckets (security_score): agent: 3.2 Â· threat: 2.0

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 2 Low 1 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 6 9-layer 0 Crowd 0 Layer: Quality 3 Security 1 Software 2

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 3 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

3 matching findings on this repo

medium [ERR001] Silent Exception Swallowing: Silently swallowing all exceptions hides … scripts/check_audit_artifact_consistency.py:1975
medium Codex session log reader may expose prompts or tool-call content scripts/run_codex_audit.sh:26
medium Duplicated implementation block across source files scripts/check_compliance_report.py:57

View all fragile runtime findings →

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/03b24a0c-a977-4e59-a04d-4c85f0722e2d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/03b24a0c-a977-4e59-a04d-4c85f0722e2d/

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.