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

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
Combined
76.4
/100
Security checks
76
0 findings
System graph
76
55.6% cov · 639 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 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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Insecure pattern 'eval_used' in tools/fuzz_differential.py:1181
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
tools/fuzz_differential.py:1181
#2
Insecure pattern 'exec_used' in tools/fuzz_differential.py:1798
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
tools/fuzz_differential.py:1798
#3
Insecure pattern 'exec_used' in benchmarking/audit_bindings.py:107
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/audit_bindings.py:107
#4
Insecure pattern 'exec_used' in benchmarking/generate_ds1000_numpy_kernels.py:269
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/generate_ds1000_numpy_kernels.py:269
#5
Insecure pattern 'exec_used' in benchmarking/ds1000_case0387/record.json:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/ds1000_case0387/record.json:2
#6
Insecure pattern 'exec_used' in benchmarking/ds1000_case0344/record.json:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/ds1000_case0344/record.json:2
#7
Insecure pattern 'exec_used' in benchmarking/ds1000_case0304/record.json:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/ds1000_case0304/record.json:2
#8
Insecure pattern 'exec_used' in benchmarking/ds1000_case0485/record.json:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/ds1000_case0485/record.json:2
#9
Insecure pattern 'exec_used' in benchmarking/ds1000_case0509/record.json:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/ds1000_case0509/record.json:2
#10
Insecure pattern 'exec_used' in benchmarking/ds1000_case0462/record.json:2
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
benchmarking/ds1000_case0462/record.json:2

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.