fern-api/fern — 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

202 of your 327 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 55.1s for a 716.9 MB repo slow.
Repobility's analysis ran in 389.83s after the clone landed.

fern-api/fern

https://github.com/fern-api/fern · scanned 2026-06-05 21:46 UTC (4 days, 11 hours ago) · 10 languages

7307 raw signals (315 security + 6992 graph) 11/13 scanners ran 10th percentile · Typescript · huge (>500K LoC) System graph score 40 (higher by 33)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 11 hours ago · v2 · 1138 actionable findings from 2 signal sources. 2652 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 · 1053 findings

click to filter

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	100.0	0.25	25.00
`testing_score`	50.0	0.20	10.00
`documentation_score`	89.0	0.15	13.35
`practices_score`	69.0	0.15	10.35
`code_quality`	51.0	0.10	5.10
Overall		1.00	72.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 5 High 32 Medium 36 Low 402 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 85 System graph 1053 Crowd 0 Layer: Quality 953 Cicd 11 Software 10 Security 18 Frontend 128 Hardware 3 Api 15

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 packages/seed/src/utils/getGeneratorInvocation.ts

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 packages/seed/src/utils/getGeneratorInvocation.ts:185; move to env var / secrets manager.

packages/seed/src/utils/getGeneratorInvocation.ts:185

#2

Possible secret in packages/seed/src/utils/getGeneratorInvocation.ts

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 packages/seed/src/utils/getGeneratorInvocation.ts:192; move to env var / secrets manager.

packages/seed/src/utils/getGeneratorInvocation.ts:192

#3

Possible secret in seed/python-sdk/oauth-client-credentials-openapi/src/seed/identity/client.py

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 seed/python-sdk/oauth-client-credentials-openapi/src/seed/identity/client.py:58; move to env var / secrets manager.

seed/python-sdk/oauth-client-credentials-openapi/src/seed/identity/client.py:58

#4

Possible secret in seed/python-sdk/oauth-client-credentials-openapi/src/seed/identity/client.py

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 seed/python-sdk/oauth-client-credentials-openapi/src/seed/identity/client.py:114; move to env var / secrets manager.

seed/python-sdk/oauth-client-credentials-openapi/src/seed/identity/client.py:114

#5

Possible secret in seed/python-sdk/request-parameters/src/seed/user/client.py

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 seed/python-sdk/request-parameters/src/seed/user/client.py:70; move to env var / secrets manager.

seed/python-sdk/request-parameters/src/seed/user/client.py:70

#6

Possible secret in seed/python-sdk/request-parameters/src/seed/user/client.py

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 seed/python-sdk/request-parameters/src/seed/user/client.py:116; move to env var / secrets manager.

seed/python-sdk/request-parameters/src/seed/user/client.py:116

#7

Possible secret in seed/python-sdk/request-parameters/src/seed/user/client.py

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 seed/python-sdk/request-parameters/src/seed/user/client.py:362; move to env var / secrets manager.

seed/python-sdk/request-parameters/src/seed/user/client.py:362

#8

Possible secret in seed/python-sdk/request-parameters/src/seed/user/client.py

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 seed/python-sdk/request-parameters/src/seed/user/client.py:416; move to env var / secrets manager.

seed/python-sdk/request-parameters/src/seed/user/client.py:416

#9

Possible secret in seed/python-sdk/client-side-params/src/seed/service/client.py

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 seed/python-sdk/client-side-params/src/seed/service/client.py:394; move to env var / secrets manager.

seed/python-sdk/client-side-params/src/seed/service/client.py:394

#10

Possible secret in seed/python-sdk/client-side-params/src/seed/service/client.py

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 seed/python-sdk/client-side-params/src/seed/service/client.py:480; move to env var / secrets manager.

seed/python-sdk/client-side-params/src/seed/service/client.py:480

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/9d3569bc-0fef-45ea-8b24-61a37a6dbd1a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/9d3569bc-0fef-45ea-8b24-61a37a6dbd1a/

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.