From 78b9c88edd03e8717b881b1d08bf143d87509c4a Mon Sep 17 00:00:00 2001
From: Sung Ye In <66503450+syi0808@users.noreply.github.com>
Date: Fri, 18 Oct 2024 15:04:12 +0900
Subject: [PATCH] docs: add badges on readme

---
 README.md | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f29cf83..040e803 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,15 @@
 <img src="https://github.com/syi0808/pubm/blob/main/docs/logo.svg" height="150">
 </p>
 
+<p align="center">
+  <a href="https://www.npmjs.com/package/pubm">
+    <img src="https://img.shields.io/npm/v/pubm" alt="npm version" />
+  </a> 
+  <a href="https://jsr.io/@pubm/pubm">
+    <img src="https://jsr.io/badges/@pubm/pubm/score" alt="jsr version" />
+  </a>
+</p>
+
 <h1 align="center">
 pubm
 </h1>
@@ -160,4 +169,4 @@ The only way to access jsr’s certified environment is through a direct API req
 
 The jsr token is encrypted and stored using various layers of information. As long as you have control over the local machine where pubm was run, it is highly unlikely the token can be compromised.
 
-If you prefer not to save tokens, you can use the `--no-save-token` option, which will request the token each time.
\ No newline at end of file
+If you prefer not to save tokens, you can use the `--no-save-token` option, which will request the token each time.