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.

cipherinsight/zinnia

https://github.com/cipherinsight/zinnia · scanned 2026-06-17 01:51 UTC (1 month, 1 week ago)

657 raw signals (0 security + 657 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -0.3 (diff) · 639 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

55.6% cov · 639 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 389 Medium 9 Low 65 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 639 Crowd 0 Layer: Software 30 Network 2 Security 390 Quality 217

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 2 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.

2 matching findings on this repo

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

View all duplicates & near-duplicates findings →

Commented-out code 176 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 (5 lines) in tools/fuzz_differential.py:186
info Commented-code block (7 lines) in benchmarking/combine_halo2_results.py:28
info Commented-code block (5 lines) in benchmarking/run_zinnia_halo2.py:195
info Commented-code block (5 lines) in benchmarking/audit_bindings.py:53
info Commented-code block (5 lines) in benchmarking/run_halo2_baselines.py:1063
info Commented-code block (9 lines) in benchmarking/generate_ds1000_numpy_kernels.py…
info Commented-code block (8 lines) in benchmarking/ds1000_numpy_scope.py:403
info Commented-code block (9 lines) in benchmarking/run_zinnia_noir.py:185
info Commented-code block (7 lines) in benchmarking/pythran_laplace/kernel.py:2
info Commented-code block (7 lines) in benchmarking/pythran_ccopy/kernel.py:2
info Commented-code block (8 lines) in benchmarking/pythran_insertion_sort/kernel.py…
info Commented-code block (6 lines) in benchmarking/npbench_polybench_jacobi_1d_jaco…

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/895a8f03-856c-4dc9-9f85-e019c1854897/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/895a8f03-856c-4dc9-9f85-e019c1854897/

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.