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

fastlane/fastlane

https://github.com/fastlane/fastlane.git · scanned 2026-05-16 13:31 UTC (1 day, 4 hours ago) · 10 languages

383 findings (20 legacy + 363 scanner) 8/10 scanners ran Scanner says 70 (lower by 8)

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

Complete repo analysis

Last scanned 1 day, 7 hours ago · v3 · 141 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON
Combined
69.1
/100
Repobility
68
20 legacy
9-layer
71
88.9% cov · 121 gaps
Critical
70
click to filter
Agents
6
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 70 High 10 Medium 30 Low 24 Source: Legacy 20 9-layer 121 Crowd 0 Layer: Quality 20 Software 5 Api 1 Network 1 Frontend 1 Security 98 Cicd 15

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

#1
Possible secret in fastlane/lib/fastlane/actions/unlock_keychain.rb
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 fastlane/lib/fastlane/actions/unlock_keychain.rb:113; move to env var / secrets manager.
fastlane/lib/fastlane/actions/unlock_keychain.rb:113
#2
Possible secret in fastlane/lib/fastlane/actions/unlock_keychain.rb
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 fastlane/lib/fastlane/actions/unlock_keychain.rb:117; move to env var / secrets manager.
fastlane/lib/fastlane/actions/unlock_keychain.rb:117
#3
Possible secret in fastlane/lib/fastlane/actions/unlock_keychain.rb
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 fastlane/lib/fastlane/actions/unlock_keychain.rb:122; move to env var / secrets manager.
fastlane/lib/fastlane/actions/unlock_keychain.rb:122
#4
Possible secret in fastlane/lib/fastlane/actions/unlock_keychain.rb
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 fastlane/lib/fastlane/actions/unlock_keychain.rb:127; move to env var / secrets manager.
fastlane/lib/fastlane/actions/unlock_keychain.rb:127
#5
Possible secret in fastlane/lib/fastlane/actions/upload_to_testflight.rb
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 fastlane/lib/fastlane/actions/upload_to_testflight.rb:84; move to env var / secrets manager.
fastlane/lib/fastlane/actions/upload_to_testflight.rb:84
#6
Possible secret in fastlane/lib/fastlane/actions/onesignal.rb
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 fastlane/lib/fastlane/actions/onesignal.rb:184; move to env var / secrets manager.
fastlane/lib/fastlane/actions/onesignal.rb:184
#7
Possible secret in fastlane/lib/fastlane/actions/onesignal.rb
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 fastlane/lib/fastlane/actions/onesignal.rb:196; move to env var / secrets manager.
fastlane/lib/fastlane/actions/onesignal.rb:196
#8
Possible secret in fastlane/lib/fastlane/actions/artifactory.rb
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 fastlane/lib/fastlane/actions/artifactory.rb:79; move to env var / secrets manager.
fastlane/lib/fastlane/actions/artifactory.rb:79
#9
Possible secret in fastlane/lib/fastlane/actions/nexus_upload.rb
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 fastlane/lib/fastlane/actions/nexus_upload.rb:208; move to env var / secrets manager.
fastlane/lib/fastlane/actions/nexus_upload.rb:208
#10
Possible secret in fastlane/lib/fastlane/actions/nexus_upload.rb
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 fastlane/lib/fastlane/actions/nexus_upload.rb:222; move to env var / secrets manager.
fastlane/lib/fastlane/actions/nexus_upload.rb:222

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.

{# ── 2026-05-17 Round 14: AI-agent bridge footer ────────────────────── Discoverability: the /agents/voting/ guide + MCP manifest exist but aren't linked from anywhere users actually land. Small, opt-in footer. #}
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/2365195e-4868-4912-8920-a579d4df5cfd/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/2365195e-4868-4912-8920-a579d4df5cfd/

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.