pola-rs/r-polars

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.

61 of your 69 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 1.59s · analysis 15.25s · 3.9 MB · GitHub API rate-limit (preflight)

https://github.com/pola-rs/r-polars · scanned 2026-06-05 15:04 UTC (1 week, 2 days ago) · 10 languages

128 raw signals (62 security + 66 graph) 33rd percentile · Rust · small (2-20K LoC) System graph score 87 (lower by 22)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 34 actionable findings from 2 signal sources. 61 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 11 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	80.0	0.15	12.00
`security_score`	96.5	0.25	24.12
`testing_score`	0.0	0.20	0.00
`documentation_score`	59.6	0.15	8.94
`practices_score`	84.0	0.15	12.60
`code_quality`	67.9	0.10	6.79
Overall		1.00	64.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 5 High 8 Medium 4 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 23 System graph 11 Crowd 0 Layer: Security 6 Software 2 Quality 19 Cicd 5 Api 1 Frontend 1

Exclude dismissed / FP Exclude test files

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

Insecure pattern 'eval_used' in src/rust/src/expr/array.rs:130

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

src/rust/src/expr/array.rs:130

Insecure pattern 'eval_used' in src/rust/src/expr/list.rs:123

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

src/rust/src/expr/list.rs:123

Insecure pattern 'eval_used' in src/rust/src/series/general.rs:285

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

src/rust/src/series/general.rs:285

Insecure pattern 'eval_used' in src/rust/src/lazyframe/general.rs:118

GapSeverity.HIGH Layer.SECURITY score 0.413

Why: high severity · OWASP-class risk

src/rust/src/lazyframe/general.rs:118

GitHub Action tracks a moving branch

GapSeverity.HIGH Layer.CICD score 0.375

Why: high severity

.github/workflows/build-wasm.yml:21

No auth library detected

GapSeverity.MEDIUM Layer.SECURITY score 0.338

Why: medium severity

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/build-docs.yml:98

GitHub Actions workflow grants broad write permissions

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/build-docs.yml

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/release-lib.yml:91

#10

GitHub Action is tag-pinned rather than SHA-pinned

GapSeverity.MEDIUM Layer.CICD score 0.225

Why: medium severity

.github/workflows/release-lib.yml:242

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/795fcf73-d2bf-4a9c-aefa-5b3041d0caa2/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/795fcf73-d2bf-4a9c-aefa-5b3041d0caa2/

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.