zapplyjobs/New-Grad-Jobs-2026

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.

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

Scan timing: clone 29.45s · analysis 0.15s · 77.1 MB · GitHub API rate-limit (preflight)

https://github.com/zapplyjobs/New-Grad-Jobs-2026 · scanned 2026-06-05 12:58 UTC (5 days, 9 hours ago) · 10 languages

62 raw signals (20 security + 42 graph) 11/13 scanners ran 53rd percentile · Javascript · tiny (<2K LoC) System graph score 85 (lower by 23)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 9 hours ago · v2 · 21 actionable findings from 2 signal sources. 20 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`	55.0	0.15	8.25
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	72.0	0.15	10.80
`practices_score`	65.0	0.15	9.75
`code_quality`	80.0	0.10	8.00
Overall		1.00	61.8

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 0 Medium 5 Low 11 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 10 System graph 11 Crowd 0 Layer: Quality 10 Cicd 2 Software 3 Api 1 Frontend 4 Security 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.

Config drift 1 finding

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.

1 matching finding on this repo

low File has no detected symbols: .github/scripts/job-fetcher/config.js

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/ac9033f3-a941-41bf-bedb-fe44aa1a556d/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ac9033f3-a941-41bf-bedb-fe44aa1a556d/

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.