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

ropensci/FedData

https://github.com/ropensci/FedData · scanned 2026-06-15 23:55 UTC (2 months, 3 weeks ago)

47 raw signals (0 security + 47 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 47 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
91.1
/100
Security checks
91
0 findings
System graph
91
77.8% cov · 47 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 1 Medium 21 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 47 Crowd 0 Layer: Frontend 14 Network 1 Security 12 Cicd 1 Quality 19
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 91.1/100 with 77.8% coverage. It contains 769 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 47 findings — concentrated in quality (19), frontend (14), security (12). Risk profile is high: 0 critical, 1 high, 21 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 36 of 47 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security security conf 1.00 Insecure pattern 'eval_used' in docs/articles/FedData_files/joda-0.0.1/joda.js:9
Found a known-risky pattern (eval_used). Review and replace if possible.
docs/articles/FedData_files/joda-0.0.1/joda.js:9 Eval used
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/articles/FedData_files/FlatGeoBuf-3.21.3/fgb.js:142
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/articles/FedData_files/FlatGeoBuf-3.21.3/flatgeobuf-geojson.min.js:16
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/articles/FedData_files/FlatGeoBuf-3.31.1/fgb.js:173
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/articles/FedData_files/FlatGeoBuf-3.31.1/flatgeobuf-geojson.min.js:15
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/pkgdown.js:93
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Tests conf 1.00 CI is configured but no tests are detected
A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.
CI/CDConfig theaterRepo hardening
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 GitHub Action is tag-pinned rather than SHA-pinned
JamesIves/github-pages-deploy-action@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
.github/workflows/pkgdown.yaml:42 CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/articles/FedData_files/joda-0.0.1/joda.js:16
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/articles/FedData_files/joda-0.0.1/joda.js:16 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/articles/FedData_files/leaflet-1.3.1/leaflet.js:5
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/articles/FedData_files/leaflet-1.3.1/leaflet.js:5 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/articles/FedData_files/leaflet-binding-2.2.2/leaflet.js:1957
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/articles/FedData_files/leaflet-binding-2.2.2/leaflet.js:1957 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/articles/FedData_files/leaflet-binding-2.2.3/leaflet.js:1957
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/articles/FedData_files/leaflet-binding-2.2.3/leaflet.js:1957 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/deps/bootstrap-5.3.1/bootstrap.bundle.min.js:6
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/deps/bootstrap-5.3.1/bootstrap.bundle.min.js:6 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/deps/bootstrap-5.3.8/bootstrap.bundle.min.js:6
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/deps/bootstrap-5.3.8/bootstrap.bundle.min.js:6 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/deps/jquery-3.6.0/jquery-3.6.0.js:1332
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/deps/jquery-3.6.0/jquery-3.6.0.js:1332 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/deps/jquery-3.6.0/jquery-3.6.0.min.js:2
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/deps/jquery-3.6.0/jquery-3.6.0.min.js:2 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in docs/deps/bootstrap-5.3.1/bootstrap.bundle.min.js:6
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
docs/deps/bootstrap-5.3.1/bootstrap.bundle.min.js:6 Domparser html parse
medium System graph security security conf 1.00 Insecure pattern 'domparser_html_parse' in docs/deps/bootstrap-5.3.8/bootstrap.bundle.min.js:6
Found a known-risky pattern (domparser_html_parse). Review and replace if possible.
docs/deps/bootstrap-5.3.8/bootstrap.bundle.min.js:6 Domparser html parse
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph network Security conf 1.00 Privileged port 51 in use
Port 51 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
docs/pkgdown.yml Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
0 test file(s) for 34 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 19 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `pdataOld` in docs/deps/jquery-3.6.0/jquery-3.6.0.js:5988
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/clipboard-0.0.1/setClipboardText.js:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/FlatGeoBuf-3.21.3/fgb.js:175
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/FlatGeoBuf-3.31.1/fgb.js:204
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/htmlwidgets-1.6.4/htmlwidgets.js:86
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/joda-0.0.1/joda.js:59
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/leaflet-binding-2.2.2/leaflet.js:2752
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/leaflet-binding-2.2.3/leaflet.js:2752
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — docs/articles/FedData_files/proj4-2.6.2/proj4.min.js:1
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph quality Complexity conf 1.00 Very large file: docs/articles/FedData_files/leaflet-binding-2.2.2/leaflet.js (2787 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: docs/articles/FedData_files/leaflet-binding-2.2.3/leaflet.js (2787 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: docs/deps/jquery-3.6.0/jquery-3.6.0.js (10881 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/1fdd9774-b9cc-43df-8bf7-6b38cfa96b40/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/1fdd9774-b9cc-43df-8bf7-6b38cfa96b40/

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.