CORE // ACTIVE

CONFIDENTIAL // AUTHORIZED RECIPIENTS ONLY

REF: THRT-UNK-7729

Findings

Issues we found in the tools your business uses. You can fix most of them directly from this page.

Search findings...
Status:Open
Add filter
Group:Platform
Sort:Severity
56 open · 4 of 9 connected 56 of 89
Clear all

Connected integrations

Google Workspace

Ready for its first security assessment.

Run assessment

Cloudflare

Ready for its first security assessment.

Run assessment

Vercel

Ready for its first security assessment.

Run assessment
GitHub 56 231185
Run assessment
Critical
The default branch is not protected GH-BP-001 ThreatUnknown-Demo/marketing-site
Configuration
Fix with agent
Critical
Two-factor authentication is not required GH-ORG-002
Configuration
Guide me
High
Members are given elevated access to every repository GH-ORG-001
Configuration
Fix with agent
High
Members can create public repositories GH-ORG-005
Configuration
Fix with agent
High
Any third-party automation can run in your organisation GH-ORG-010
Configuration
Guide me
GI
Agent update
Agent session started
Your agent session has started
View agent Dismiss
Protect your main code branches
Conversations
Security Advisor
Protect your main code branches
Protect your main code branches
Getting started
Threat model
GitHub security assessment
test123
Today 1:48 PM
Agent

Agent is working...

Protect your main code branches

Needs your input

What is the name of marketing-site's main branch (e.g. "main" or "master"), and is it okay if I require at least one person to approve changes before they can be merged into it?

Type your response…
Respond
You
main and yes
Agent

Agent is working...

Protect your main code branches

Action required

Decision

Approved

Proposed changes

  • •Turn on branch protection for main in ThreatUnknown-Demo/marketing-site
  • •Require at least one person to approve changes before they can be merged into main

Current state

The main branch in marketing-site has no protection rule at all. Anyone with write access can push directly to it, and changes can be merged with no review.

Impact

Going forward, changes to main will need at least one approval before they can be merged. Nobody will be able to push straight to main without going through a pull request and getting that approval.

Rollback

The requirement for one approval can be turned back off in GitHub's branch protection settings for this repository at any time.

Planned changes (1)

mcp__agent-tools__github_set_branch_protection
branch: main
repository: ThreatUnknown-Demo/marketing-site
requiredApprovingReviewCount: 1

▸ Advanced ▸ raw tool calls

Optional: add notes (required if rejecting)…
Approve Reject
Agent

Agent is working...

Waiting for agent…
Send →
↵ ENTER TO SEND ⇧ SHIFT+ENTER FOR NEW LINE