From 8e55f739e12e61c04708367f638a54e8f0775821 Mon Sep 17 00:00:00 2001
From: kkdev92 <112151103+kkdev92@users.noreply.github.com>
Date: Thu, 13 Aug 2026 12:40:01 +0900
Subject: [PATCH] docs: show the OpenSSF Best Practices badge

The project now carries a passing badge. The badge is a self-certification, so
it is worth saying what it actually rests on: 67 criteria answered, each
justification checked against this repository rather than asserted, and the
answers kept in version control alongside the entry.

Where the honest answer was less flattering it says so - branch coverage is given
unrounded, and a criterion is left No rather than argued into a Yes.

Placed with the other badges so a reader can see the release, the build and the
self-assessment together.
---
 README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/README.md b/README.md
index 843296d..0601fec 100644
--- a/README.md
+++ b/README.md
@@ -4,6 +4,7 @@
 [![CI](https://github.com/kkdev92/vscode-ext-kit/actions/workflows/ci.yml/badge.svg)](https://github.com/kkdev92/vscode-ext-kit/actions)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 [![TypeScript](https://img.shields.io/badge/TypeScript-6.0-blue.svg)](https://www.typescriptlang.org/)
+[![OpenSSF Best Practices](https://www.bestpractices.dev/projects/14048/badge)](https://www.bestpractices.dev/projects/14048)
 
 An application framework for VS Code extensions. You declare what your extension
 is made of; the framework validates that declaration before touching VS Code,