All teardowns
microsoft logo

Free Verify scan · microsoft/semantic-kernel

semantic-kernel scores 69/100

SDK for AI agents and plugins (succeeded by Microsoft Agent Framework).

Commit 7e68276 · 132 controls · Oct 16, 2026 · Re-checked daily

Scanned with public access only. Customer results are never published.

Delivery controls score69
semantic-kernel
42median 6886

Out of 100. Stronger than 54% of the 68 other assessed repositories.

Score

69/100

Rank 29 of 69 · median 68

Gaps

32

1 fewer than the median of 33

Critical

4 controls

2 root causes

Not visible

13

Needs admin access

What semantic-kernel does wellDefault branch identifiedBranch strategy observableDefault branch protected by rulesetForce-push restrictedPull-request requirement on default branch
Gaps32
semantic-kernel
15median 3361

Visible controls Verify found unmet. Fewer is better. Stronger than 51% of the 68 other assessed repositories.

How does your team compare?

This is what Canon Verify found in semantic-kernel's public configuration. Your team's process probably has the same gaps. Most private repos do.

See how your team scores

5 minutes. No repository access needed.

Scan your own repo with Verify (free)

Analysis

Our read

01

Governance leads the assessment.

9 of 10 visible controls pass in governance.

02

Agents & AI has the most room to improve.

1 visible control remain open in agents & ai.

Priority

Fix these first

critical

Production approvers named

Covers 3 controls
  • Production approvers named
  • Production protection
  • Production reviewers resolved

What Verify read

No resolved production reviewers.

Risk: Unnamed production approvers mean deployment approval falls to whoever is nearby when the button needs pressing.

text
Name production reviewers.

Have this gap too? Start from the PR Review Pipeline flow.

Open in Design
critical

Required checks match workflow names

Covers 4 controls
  • Required checks match workflow names
  • Required status checks strict
  • Required check includes tests
  • Required lint check

What Verify read

Required checks: none

Risk: If required checks do not match the jobs that run, a rule appears to protect the branch while enforcing nothing.

text
Align required checks with jobs.
high

CODEOWNERS reviews required

Covers 1 control
  • CODEOWNERS reviews required

What Verify read

Code-owner reviews: false

Risk: Without required code-owner review, a change to a sensitive area can be approved by someone unfamiliar with it.

text
Require code-owner review.

Overview

Control map

Public-access limit

13 controls this scan couldn't read

This free scan used public access only. These controls live in settings only a repository admin can read. Verify checks them on your connected repository.

  • Administrator bypass restrictedhigh
  • Tag protectionhigh
  • Self-merge restrictedhigh
  • Bypass actors justifiedhigh
  • Push protection enabledhigh
  • Dependabot alertshigh
  • Secret scanning alertshigh
  • SAST required on default branchhigh
  • Environment secrets scopedhigh
  • Secret custodiansmedium
  • Audit of privileged actionsmedium
  • Private vulnerability reportinglow
  • Wait timer or freeze windowlow
Get Verify

Method

How Verify works

01

Read

Verify reads the repository at a pinned commit: settings, rulesets, workflows, and files.

02

Judge

Each control is checked against a written expectation. Same inspector, same criteria, every repository.

03

Prove

Every result shows the evidence Verify read. Assessments re-run daily, and changes are logged.

132 controls · 69 repositories assessed · re-run daily

This free scanVerify on your repository
AccessPublicGitHub App you install
Controls read103 of 103All 103
Private repositoriesNoYes
ResultsPublished herePrivate to your organization

Evidence locker

Every control Verify checked

Governance

9 of 12 pass

Review

20 of 26 pass

CI & tests

19 of 30 pass

Code quality

2 of 8 pass

Security

9 of 20 pass

Agents & AI

0 of 8 pass

Release & ops

8 of 22 pass

Docs

4 of 6 pass

Assessment timeline

Canon re-assesses this repository daily. An entry appears only when something changed — the score, a control's outcome, or a control ceasing to apply.

Sep 21 · 68Oct 16 · 69
  • Oct 1, 2026Delivery controls score 68 → 6958ad1a3
  • Oct 1, 2026Stale reviews dismissed · Review — gap → confirmed58ad1a3
  • Sep 27, 2026SBOM or dependency graph · Security — needs repository admin access → confirmedca40aa7
  • Sep 25, 2026SBOM or dependency graph · Security — confirmed → needs repository admin accessca40aa7

Get this report for your own repository.

Canon Verify runs the same inspection on your private repo. Read-only GitHub App. First scan free.

Read-only access. No code stored. How Canon handles your data →

View microsoft/semantic-kernel on GitHub

Maintain semantic-kernel? If anything here is inaccurate or out of date, email security@strikelabs.co and we'll correct it.