我們掃描的內容
- Repository visibility, collaborator and team access (never source code)
- Installed GitHub Apps / OAuth apps and their granted scopes
- Deploy keys per repository, including whether each key is read-only
唯讀監控——除非您開啟自動修復並單獨授予寫入存取權，否則 GitHub 資料中的任何內容都不會改變。
安全發現結果
每次 GitHub 掃描時會執行 26 個偵測規則。每個發現結果都附帶純文字說明、背後的證據和修復步驟。
- CRITICALPublic exposure
Public link with edit/owner access
- CRITICALExternal access
External principal holds ownership
- HIGHPublic exposure
Public link share (link-only)
- HIGHPublic exposure
Public + web-discoverable share
- HIGHExternal access
External access to sensitive data
- HIGHExternal access
External collaborator with edit access
- HIGHOver permission
Sensitive resource editable org-wide
- HIGHOver permission
Broad group access to sensitive data
- HIGHAI agent
Service account with broad write access
- HIGHAI agent
AI agent with access to sensitive data
- HIGHAI agent
AI agent with edit/owner access
- HIGHExternal access
Access granted to a look-alike (typosquat) domain
- HIGHStale access
Copilot seat assigned to a departed member
- HIGHOver permission
Installed GitHub App holds write or admin permissions
- HIGHOver permission
Deploy key with write access
- MEDIUMOver permission
Broad org-wide edit access (aggregate)
- MEDIUMOver permission
Resource with multiple owners
- MEDIUMStale access
Stale external read access
- MEDIUMStale access
Dormant privileged internal account
- MEDIUMMisconfig
Direct share breaks folder inheritance
- MEDIUMMisconfig
GitHub Copilot allows suggestions that match public code
- MEDIUMStale access
Copilot seat unused for 90+ days
- MEDIUMStale access
Write-capable GitHub App looks abandoned
- MEDIUMExternal access
Public repository has collaborators with write access
- MEDIUMMisconfig
Vendor AI-training data-contribution posture
- LOWMisconfig
Copilot seats auto-assigned to all members
Related guide
如何連接 GitHub
步驟 1
登入 8200.dev 或建立帳戶
步驟 2
前往連接器 → GitHub
步驟 3
按一下「連接」並透過 GitHub 的同意畫面授權
步驟 4
8200.dev 自動掃描——結果在幾分鐘內出現
在幾分鐘內連接您的第一個來源——免費、唯讀、無銷售電話。