Stirling-Tools/Stirling-PDF — Repobility public scan

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

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

Upstream (GitHub) caused delay on this scan — not Repobility.

GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
Clone from GitHub took 106.44s for a 179.0 MB repo slow.
Repobility's analysis ran in 30.7s after the clone landed.

Stirling-Tools/Stirling-PDF

https://github.com/Stirling-Tools/Stirling-PDF · scanned 2026-06-05 07:26 UTC (5 days, 22 hours ago) · 10 languages

4361 raw signals (281 security + 4080 graph) 11/13 scanners ran 59th percentile · Typescript · huge (>500K LoC) System graph score 53 (higher by 33)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

Security checks

100.0% cov · 411 findings

click to filter

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	65.0	0.15	9.75
`security_score`	100.0	0.25	25.00
`testing_score`	80.0	0.20	16.00
`documentation_score`	95.0	0.15	14.25
`practices_score`	92.0	0.15	13.80
`code_quality`	73.0	0.10	7.30
Overall		1.00	86.1

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 54 High 50 Medium 46 Low 248 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 100 System graph 411 Crowd 0 Layer: Quality 167 Security 88 Cicd 9 Software 70 Frontend 111 Network 4 Hardware 5 Api 57

Exclude dismissed / FP Exclude test files

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

#1

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:100; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:100

#2

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:157; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:157

#3

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:160; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:160

#4

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:161; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:161

#5

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:164; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:164

#6

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:165; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:165

#7

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:2163; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:2163

#8

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:2315; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:2315

#9

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:2507; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:2507

#10

Possible secret in frontend/editor/public/locales/pt-PT/translation.toml

GapSeverity.CRITICAL Layer.SECURITY score 1.000

Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in frontend/editor/public/locales/pt-PT/translation.toml:2509; move to env var / secrets manager.

frontend/editor/public/locales/pt-PT/translation.toml:2509

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/aeb22723-45c8-4d6f-af4d-b72b584ba6d4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/aeb22723-45c8-4d6f-af4d-b72b584ba6d4/

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.