Skip to main content

Browse the directory

Showing 2 resources for "branch-protection"
Saved
Active

Privacy notes filter active — add entries to compare trust side by side.

Rollout signal scan

2 rollout risk signals in current results

Biggest gaps: metadata review, package integrity. 0 entries have 2+ required gaps.

2 scanned

Install payload

Install payload is broadly covered in current results.

good

100% (2/2)

Adoption queue

Browse adoption queue · balanced

0/2 visible results are ready for staged adoption under this preset.

ready 0caution 2hold 0

Git Branch Protection - Hooks

1 blockers: Metadata review

caution

50/100

Request metadata review from maintainers or internal owners.

Collect package checksum or signed artifact information.

hooks/git-branch-protection · trust review · confidence 67%

High-Risk Code Review Escalation Rules

1 blockers: Metadata review

caution

50/100

Request metadata review from maintainers or internal owners.

Collect package checksum or signed artifact information.

rules/high-risk-code-review-escalation-rules · trust review · confidence 67%

Decision confidence

Decision confidence scan · balanced

0/2 results are high-confidence for the selected preset.

high 0medium 2low 0

Git Branch Protection - Hooks

Address Metadata review, Package integrity before broader rollout.

medium

54/100

Missing: Metadata reviewMissing: Package integrity

hooks/git-branch-protection · trust review

High-Risk Code Review Escalation Rules

Address Metadata review, Package integrity before broader rollout.

medium

54/100

Missing: Metadata reviewMissing: Package integrity

rules/high-risk-code-review-escalation-rules · trust review

Freshness distribution

50% of this view is aging or stale

Median age 183 days; 1 fresh of 2 scanned. Re-verify the oldest entries.

median 183d

Aging

91–180 days

0%

0 entries

Stale

> 180 days

50%

1 entry

Oldest entries in this view

Source-backed rules for deciding when an AI-assisted code review must escalate high-risk changes to security, infrastructure, data, release, or domain owners before merge.

Prevents direct edits to protected branches like main or master, enforcing PR-based workflows.

Trigger:PreToolUse
Safety ✓ Privacy ✓