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.

anicka-net/ossuary-risk

https://github.com/anicka-net/ossuary-risk · scanned 2026-06-17 01:33 UTC (1 month, 2 weeks ago)

79 raw signals (0 security + 79 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 61 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 1 Medium 5 Low 32 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 61 Crowd 0 Layer: Software 22 Security 1 Cicd 1 Quality 37

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.

Duplicates & near-duplicates 3 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

3 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places
low Near-duplicate function bodies in 5 places repo-level

View all duplicates & near-duplicates findings →

Commented-out code 21 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in tests/test_sentiment.py:206
info Commented-code block (6 lines) in tests/test_scoring.py:317
info Commented-code block (5 lines) in tests/test_doc_code_drift.py:552
info Commented-code block (10 lines) in scripts/validate.py:67
info Commented-code block (5 lines) in scripts/migrate_scores_nullable.py:73
info Commented-code block (5 lines) in src/ossuary/cli.py:832
info Commented-code block (8 lines) in src/ossuary/dashboard/utils.py:17
info Commented-code block (5 lines) in src/ossuary/dashboard/pages/4_Methodology.py:…
info Commented-code block (7 lines) in src/ossuary/scoring/reputation.py:75
info Commented-code block (14 lines) in src/ossuary/scoring/factors.py:195
info Commented-code block (8 lines) in src/ossuary/scoring/engine.py:129
info Commented-code block (5 lines) in src/ossuary/collectors/git.py:184

View all commented-out code 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/c1ace448-c314-4675-ad5b-0e4b11d75f18/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c1ace448-c314-4675-ad5b-0e4b11d75f18/

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.