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
15 of your 52 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

mozilla/pdf.js

https://github.com/mozilla/pdf.js · scanned 2026-06-05 11:07 UTC (1 week, 1 day ago) · 10 languages

574 raw signals (46 security + 528 graph) 11/13 scanners ran 38th percentile · Javascript · large (100-500K LoC) System graph score 83 (lower by 9)

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

Complete repo analysis

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

JSON
Combined
86.9
/100
Security checks
91
17 findings
System graph
83
100.0% cov · 258 findings
Critical
3
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 100.0 0.15 15.00
security_score 100.0 0.25 25.00
testing_score 44.0 0.20 8.80
documentation_score 62.0 0.15 9.30
practices_score 69.0 0.15 10.35
code_quality 50.0 0.10 5.00
Overall 1.00 73.5
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: layer: cicd × excluding tests × Reset all
Severity: Critical 3 High 11 Medium 34 Low 94 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 17 System graph 258 Crowd 0 Layer: Quality 136 Security 14 Software 52 Cicd 3 Api 1 Frontend 69
Scan summary Quality grade B (74/100). Dimensions: security 100, maintainability 100. 46 findings (7 security). 155,760 lines analyzed.

Showing 3 of 275 actionable findings. 309 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

low Security checks cicd CI/CD security conf 0.35 ✓ Repobility 4 occurrences Workflow references repository secrets in a pull_request workflow
Fork pull_request runs do not receive normal repository secrets on GitHub Actions. Review this as a reliability/intent signal, not as direct fork-secret exfiltration. Raise severity only for pull_request_target or another trusted-context path that runs untrusted PR code with secrets.
4 files, 4 locations
.github/workflows/coverage_browser_tests.yml:92
.github/workflows/font_tests.yml:76
.github/workflows/integration_tests.yml:99
.github/workflows/unit_tests.yml:86
CI/CD securityworkflow secretsGitHub Actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/publish_website.yml CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/publish_release.yml CI/CD securitySupply chainGithub actions
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/2f74ab68-f443-492b-a9d6-3f4280151f6a/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2f74ab68-f443-492b-a9d6-3f4280151f6a/

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.