我们扫描的内容
- 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 自动扫描——数分钟内即可看到结果
几分钟内接入您的第一个数据源——免费、只读，无需销售沟通。