oracle/graalvm-reachability-metadata

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.

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

Scan timing: clone 18.58s · analysis 20.65s · 62.3 MB · GitHub API rate-limit (preflight)

https://github.com/oracle/graalvm-reachability-metadata · scanned 2026-06-05 20:44 UTC (4 days, 13 hours ago) · 10 languages

396 raw signals (122 security + 274 graph) 11/13 scanners ran 57th percentile · Java · large (100-500K LoC) System graph score 84 (lower by 7)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 116 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	40.0	0.15	6.00
`security_score`	100.0	0.25	25.00
`testing_score`	90.0	0.20	18.00
`documentation_score`	75.0	0.15	11.25
`practices_score`	74.0	0.15	11.10
`code_quality`	56.0	0.10	5.60
Overall		1.00	76.9

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 7 Medium 61 Low 57 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 50 System graph 116 Crowd 0 Layer: Software 30 Quality 96 Security 34 Frontend 3 Network 2 Cicd 1

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 3 places repo-level
low Near-duplicate function bodies in 2 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

high [MINED106] Phantom test coverage: test_count_test_only_metadata_entries_rejects… forge/tests/test_metrics_paths.py:395

View all legacy markers findings →

Commented-out code 3 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/`.

3 matching findings on this repo

info Commented-code block (6 lines) in forge/ai_workflows/core/workflow_strategy.py:…
info Commented-code block (7 lines) in forge/utility_scripts/local_ci_verification.p…
info Commented-code block (7 lines) in .github/actions/detect-file-changes/detect-fi…

View all commented-out code findings →

Config drift 2 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

2 matching findings on this repo

high [MINED106] Phantom test coverage: test_count_test_only_metadata_entries_rejects… forge/tests/test_metrics_paths.py:395
medium Network/subprocess call without timeout or try/except — forge/utility_scripts/n…

View all config drift 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/bcbb13c9-a034-4744-989c-05436b288eb4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/bcbb13c9-a034-4744-989c-05436b288eb4/

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.