@mcptoolshop/brand 0.1.2 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.es.md CHANGED
@@ -2,54 +2,62 @@
2
2
  <a href="README.ja.md">日本語</a> | <a href="README.zh.md">中文</a> | <a href="README.md">English</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
3
3
  </p>
4
4
 
5
- <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
7
- </p>
5
+ <p align="center">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
+ </p>
8
+
9
+ <p align="center">
10
+ <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
+ <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
13
+ <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
14
+ </p>
8
15
 
9
- <p align="center">
10
- <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
12
- <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
13
- </p>
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
14
20
 
15
- Registro centralizado de activos de marca para la organización GitHub [mcp-tool-shop-org](https://github.com/mcp-tool-shop-org). Un repositorio contiene todos los logotipos. Cada archivo README hace referencia a este repositorio. Actualiza una vez, y se actualiza en todas partes.
21
+ ---
16
22
 
17
23
  ## ¿Por qué?
18
24
 
19
- Cuando cada repositorio tiene su propia copia del logotipo, se produce duplicación, desviación e inconsistencia. Una actualización de la marca implica buscar en más de 80 repositorios. Este repositorio soluciona ese problema: los logotipos se encuentran aquí, y los archivos README los referencian a través de URLs de `raw.githubusercontent.com`.
25
+ Cuando cada repositorio tiene su propia copia del logotipo, se produce duplicación, divergencia e inconsistencia. Una renovación de marca implica buscar en más de 100 repositorios. Este repositorio soluciona ese problema: los logotipos se almacenan aquí, y los archivos README los referencian a través de URLs de `raw.githubusercontent.com`.
20
26
 
21
27
  ## Estructura
22
28
 
23
- ```
24
- logos/
25
- <slug>/
26
- readme.png # or readme.jpg — format preserved as-is
27
- manifest.json # SHA-256 integrity hashes for every asset
28
- docs/
29
- handbook.md # Lessons learned from migrating 80+ repos
30
- ```
29
+ ```
30
+ logos/
31
+ <slug>/
32
+ readme.png # or readme.jpg — format preserved as-is
33
+ manifest.json # SHA-256 integrity hashes for every asset
34
+ docs/
35
+ handbook.md # Lessons learned from migrating 100+ repos
36
+ ```
31
37
 
32
- 81 logotipos distribuidos en 81 repositorios. Los archivos PNG permanecen como PNG y los archivos JPEG como JPEG. El formato es una decisión de la marca, no un objetivo de compilación.
38
+ Hay 117 logotipos en toda la organización. Los archivos PNG permanecen como PNG y los archivos JPEG permanecen como JPEG. El formato es una decisión de marca, no un objetivo de compilación.
33
39
 
34
40
  ## Interfaz de línea de comandos (CLI)
35
41
 
36
- ```bash
37
- # Verify all logos match their manifest hashes
38
- brand verify
39
-
40
- # Regenerate manifest after adding/replacing a logo
41
- brand manifest
42
-
43
- # CI mode — fail if manifest is out of date
44
- brand manifest --check
45
-
46
- # Audit repos for broken refs, badge collisions, indentation traps
47
- brand audit --repos /path/to/clones
48
-
49
- # Migrate READMEs to point at brand repo (dry run first)
50
- brand migrate --repos /path/to/clones --dry-run
51
- brand migrate --repos /path/to/clones
52
- ```
42
+ ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
45
+ # Verify all logos match their manifest hashes
46
+ brand verify
47
+
48
+ # Regenerate manifest after adding/replacing a logo
49
+ brand manifest
50
+
51
+ # CI mode — fail if manifest is out of date
52
+ brand manifest --check
53
+
54
+ # Audit repos for broken refs, badge collisions, indentation traps
55
+ brand audit --repos /path/to/clones
56
+
57
+ # Migrate READMEs to point at brand repo (dry run first)
58
+ brand migrate --repos /path/to/clones --dry-run
59
+ brand migrate --repos /path/to/clones
60
+ ```
53
61
 
54
62
  ## Añadir un nuevo logotipo
55
63
 
@@ -62,8 +70,29 @@ brand migrate --repos /path/to/clones
62
70
 
63
71
  Cada logotipo está rastreado mediante un hash SHA-256 en `manifest.json`. El sistema de integración continua (CI) ejecuta `brand manifest --check` en cada push que afecte a `logos/` o `manifest.json`. Cualquier discrepancia, ya sea una sobrescritura accidental, manipulación o desviación, provoca el fallo de la compilación.
64
72
 
65
- Consulta [docs/handbook.md](docs/handbook.md) para obtener más información: por qué los enlaces simbólicos no funcionan, cómo los distintivos interfieren con la detección de logotipos, las trampas de renderizado de Markdown que rompen las etiquetas `<img>`, y el protocolo de seguridad para la migración.
73
+ Consulte [SECURITY.md](SECURITY.md) para obtener la política de seguridad completa y [docs/handbook.md](docs/handbook.md) para obtener la guía de migración.
74
+
75
+ ## Privacidad
76
+
77
+ Esta herramienta no recopila datos de telemetría. Todas las operaciones se realizan únicamente en el sistema de archivos local.
78
+
79
+ ## Evaluación
80
+
81
+ | Categoría | Puntuación | Notas |
82
+ |----------|-------|-------|
83
+ | A. Seguridad | 10/10 | SECURITY.md, integridad SHA-256, sin conexión de red, sin telemetría. |
84
+ | B. Manejo de errores | 8/10 | Errores estructurados, salida clara de la línea de comandos, códigos de salida. |
85
+ | C. Documentación para el usuario | 10/10 | README, CHANGELOG, guía, documentación completa de la línea de comandos. |
86
+ | D. Higiene en la entrega | 9/10 | Comprobación de integridad de CI, 29 pruebas, versión alineada. |
87
+ | E. Identidad | 10/10 | Logotipo, traducciones, página de inicio, metadatos. |
88
+ | **Total** | **47/50** | |
66
89
 
67
90
  ## Licencia
68
91
 
69
92
  [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/README.fr.md CHANGED
@@ -2,54 +2,62 @@
2
2
  <a href="README.ja.md">日本語</a> | <a href="README.zh.md">中文</a> | <a href="README.es.md">Español</a> | <a href="README.md">English</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
3
3
  </p>
4
4
 
5
- <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
7
- </p>
5
+ <p align="center">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
+ </p>
8
+
9
+ <p align="center">
10
+ <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
+ <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
13
+ <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
14
+ </p>
8
15
 
9
- <p align="center">
10
- <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
12
- <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
13
- </p>
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
14
20
 
15
- Registre centralisé des éléments de marque pour l'organisation GitHub [mcp-tool-shop-org](https://github.com/mcp-tool-shop-org). Un seul dépôt contient tous les logos. Chaque fichier README renvoie vers ce dépôt. Mettez à jour une seule fois, et la modification se propage partout.
21
+ ---
16
22
 
17
23
  ## Pourquoi ?
18
24
 
19
- Lorsque chaque dépôt contient sa propre copie du logo, cela entraîne une duplication, des divergences et une incohérence. Une modification de la marque implique de parcourir plus de 80 dépôts. Ce dépôt résout ce problème : les logos sont stockés ici, et les fichiers README les référencent via les URL `raw.githubusercontent.com`.
25
+ Lorsque chaque dépôt contient sa propre copie du logo, cela entraîne une duplication, des divergences et une incohérence. Une refonte de l'image de marque signifie devoir parcourir plus de 100 dépôts. Ce dépôt résout ce problème : les logos sont stockés ici, et les fichiers README y font référence via les URL `raw.githubusercontent.com`.
20
26
 
21
27
  ## Structure
22
28
 
23
- ```
24
- logos/
25
- <slug>/
26
- readme.png # or readme.jpg — format preserved as-is
27
- manifest.json # SHA-256 integrity hashes for every asset
28
- docs/
29
- handbook.md # Lessons learned from migrating 80+ repos
30
- ```
29
+ ```
30
+ logos/
31
+ <slug>/
32
+ readme.png # or readme.jpg — format preserved as-is
33
+ manifest.json # SHA-256 integrity hashes for every asset
34
+ docs/
35
+ handbook.md # Lessons learned from migrating 100+ repos
36
+ ```
31
37
 
32
- 81 logos répartis dans 81 dépôts. Les fichiers PNG restent des fichiers PNG. Les fichiers JPEG restent des fichiers JPEG. Le format est une décision de marque, et non une cible de construction.
38
+ 117 logos au sein de l'organisation. Les fichiers PNG restent des fichiers PNG. Les fichiers JPEG restent des fichiers JPEG. Le format est une décision de marque, et non une cible de construction.
33
39
 
34
40
  ## Interface en ligne de commande (CLI)
35
41
 
36
- ```bash
37
- # Verify all logos match their manifest hashes
38
- brand verify
39
-
40
- # Regenerate manifest after adding/replacing a logo
41
- brand manifest
42
-
43
- # CI mode — fail if manifest is out of date
44
- brand manifest --check
45
-
46
- # Audit repos for broken refs, badge collisions, indentation traps
47
- brand audit --repos /path/to/clones
48
-
49
- # Migrate READMEs to point at brand repo (dry run first)
50
- brand migrate --repos /path/to/clones --dry-run
51
- brand migrate --repos /path/to/clones
52
- ```
42
+ ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
45
+ # Verify all logos match their manifest hashes
46
+ brand verify
47
+
48
+ # Regenerate manifest after adding/replacing a logo
49
+ brand manifest
50
+
51
+ # CI mode — fail if manifest is out of date
52
+ brand manifest --check
53
+
54
+ # Audit repos for broken refs, badge collisions, indentation traps
55
+ brand audit --repos /path/to/clones
56
+
57
+ # Migrate READMEs to point at brand repo (dry run first)
58
+ brand migrate --repos /path/to/clones --dry-run
59
+ brand migrate --repos /path/to/clones
60
+ ```
53
61
 
54
62
  ## Ajouter un nouveau logo
55
63
 
@@ -62,8 +70,29 @@ brand migrate --repos /path/to/clones
62
70
 
63
71
  Chaque logo est suivi par un hachage SHA-256 dans `manifest.json`. L'intégration continue (CI) exécute `brand manifest --check` lors de chaque envoi qui modifie les fichiers `logos/` ou `manifest.json`. Toute incohérence – écrasement accidentel, manipulation, divergence – entraîne l'échec de la construction.
64
72
 
65
- Consultez [docs/handbook.md](docs/handbook.md) pour plus de détails : pourquoi les liens symboliques ne fonctionnent pas, comment les badges interfèrent avec la détection des logos, les pièges de rendu Markdown qui corrompent les balises `<img>`, et le protocole de sécurité de migration.
73
+ Consultez [SECURITY.md](SECURITY.md) pour la politique de sécurité complète et [docs/handbook.md](docs/handbook.md) pour le guide de migration.
74
+
75
+ ## Confidentialité
76
+
77
+ Cet outil ne collecte aucune donnée télémétrique. Toutes les opérations se déroulent uniquement sur le système de fichiers local.
78
+
79
+ ## Tableau de bord
80
+
81
+ | Catégorie | Score | Notes |
82
+ |----------|-------|-------|
83
+ | A. Sécurité | 10/10 | SECURITY.md, intégrité SHA-256, pas de réseau, pas de télémétrie. |
84
+ | B. Gestion des erreurs | 8/10 | Erreurs structurées, affichage clair de la ligne de commande, codes de sortie. |
85
+ | C. Documentation pour les utilisateurs | 10/10 | README, CHANGELOG, guide, documentation complète de la ligne de commande. |
86
+ | D. Qualité du code | 9/10 | Vérification d'intégrité CI, 29 tests, version alignée. |
87
+ | E. Identité | 10/10 | Logo, traductions, page d'accueil, métadonnées. |
88
+ | **Total** | **47/50** | |
66
89
 
67
90
  ## Licence
68
91
 
69
92
  [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/README.hi.md CHANGED
@@ -1,39 +1,47 @@
1
- <p align="center">
2
- <a href="README.ja.md">日本語</a> | <a href="README.zh.md">中文</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.md">English</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
3
- </p>
4
-
5
1
  <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
2
+ <a href="README.ja.md">日本語</a> | <a href="README.zh.md">中文</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.md">English</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
7
3
  </p>
8
-
4
+
5
+ <p align="center">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
+ </p>
8
+
9
9
  <p align="center">
10
10
  <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
11
+ <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
12
13
  <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
13
14
  </p>
14
-
15
- [mcp-tool-shop-org](https://github.com/mcp-tool-shop-org) गिटहब संगठन के लिए केंद्रीकृत ब्रांड एसेट रजिस्ट्री। एक रिपॉजिटरी में सभी लोगो मौजूद हैं। प्रत्येक README फ़ाइल यहां लिंक करती है। एक बार अपडेट करें, और हर जगह अपडेट हो जाएगा।
16
-
17
- ## क्यों?
18
-
19
- जब प्रत्येक रिपॉजिटरी में लोगो की अपनी प्रति होती है, तो डुप्लीकेशन, विचलन और असंगति होती है। ब्रांडिंग में बदलाव करने का मतलब है 80 से अधिक रिपॉजिटरी में खोज करना। यह रिपॉजिटरी इस समस्या को हल करता है - लोगो यहां मौजूद हैं, और README फ़ाइलें `raw.githubusercontent.com` यूआरएल के माध्यम से उनका उल्लेख करती हैं।
20
-
21
- ## संरचना
22
-
15
+
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
20
+
21
+ ---
22
+
23
+ ## क्यों?
24
+
25
+ जब प्रत्येक रिपॉजिटरी में लोगो की अपनी प्रतिलिपि होती है, तो इससे दोहराव, विचलन और असंगति होती है। रीब्रांडिंग का मतलब है 100 से अधिक रिपॉजिटरियों में खोज करना। यह रिपॉजिटरी इस समस्या को हल करता है - लोगो यहां मौजूद हैं, और README फ़ाइलें `raw.githubusercontent.com` यूआरएल के माध्यम से उनका संदर्भ देती हैं।
26
+
27
+ ## संरचना
28
+
23
29
  ```
24
30
  logos/
25
31
  <slug>/
26
32
  readme.png # or readme.jpg — format preserved as-is
27
33
  manifest.json # SHA-256 integrity hashes for every asset
28
34
  docs/
29
- handbook.md # Lessons learned from migrating 80+ repos
35
+ handbook.md # Lessons learned from migrating 100+ repos
30
36
  ```
31
-
32
- 81 रिपॉजिटरी में 81 लोगो। PNG फ़ाइलें PNG ही रहेंगी, और JPEG फ़ाइलें JPEG ही रहेंगी। फ़ॉर्मेट एक ब्रांड संबंधी निर्णय है, न कि बिल्ड लक्ष्य।
33
-
34
- ## कमांड-लाइन इंटरफेस (CLI)
35
-
37
+
38
+ संगठन में 117 लोगो मौजूद हैं। PNG फ़ाइलें PNG ही रहेंगी, और JPEG फ़ाइलें JPEG ही रहेंगी। फ़ॉर्मेट एक ब्रांड संबंधी निर्णय है, न कि बिल्ड लक्ष्य।
39
+
40
+ ## कमांड-लाइन इंटरफेस (CLI)
41
+
36
42
  ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
37
45
  # Verify all logos match their manifest hashes
38
46
  brand verify
39
47
 
@@ -50,20 +58,41 @@ brand audit --repos /path/to/clones
50
58
  brand migrate --repos /path/to/clones --dry-run
51
59
  brand migrate --repos /path/to/clones
52
60
  ```
53
-
54
- ## एक नया लोगो जोड़ना
55
-
56
- 1. फ़ाइल को `logos/<slug>/readme.png` (या `.jpg`) में डालें।
57
- 2. `brand manifest` कमांड चलाकर इंटीग्रिटी हैश अपडेट करें।
58
- 3. लोगो और `manifest.json` दोनों को एक साथ कमिट करें।
59
- 4. CI (निरंतर एकीकरण) सिस्टम, पुश करने पर मैनिफेस्ट को सत्यापित करता है।
60
-
61
- ## सुरक्षा
62
-
63
- प्रत्येक लोगो को `manifest.json` में SHA-256 हैश द्वारा ट्रैक किया जाता है। CI सिस्टम, `logos/` या `manifest.json` को प्रभावित करने वाले प्रत्येक पुश पर `brand manifest --check` कमांड चलाता है। किसी भी प्रकार की विसंगति - चाहे वह आकस्मिक ओवरराइट हो, छेड़छाड़ हो, या विचलन - बिल्ड को विफल कर देती है।
64
-
65
- पूरे विवरण के लिए [docs/handbook.md](docs/handbook.md) देखें: इसमें बताया गया है कि सिंबोलिक लिंक क्यों काम नहीं करते हैं, बैज लोगो का पता लगाने के साथ कैसे टकराते हैं, और मार्कडाउन रेंडरिंग के कौन से जाल `<img>` टैग को तोड़ देते हैं, साथ ही माइग्रेशन सुरक्षा प्रोटोकॉल भी।
66
-
67
- ## लाइसेंस
68
-
69
- [MIT](LICENSE)
61
+
62
+ ## एक नया लोगो जोड़ना
63
+
64
+ 1. फ़ाइल को `logos/<slug>/readme.png` (या `.jpg`) में डालें।
65
+ 2. `brand manifest` कमांड चलाकर इंटीग्रिटी हैश अपडेट करें।
66
+ 3. लोगो और `manifest.json` दोनों को एक साथ कमिट करें।
67
+ 4. CI (निरंतर एकीकरण) सिस्टम, पुश करने पर मैनिफेस्ट को सत्यापित करता है।
68
+
69
+ ## सुरक्षा
70
+
71
+ प्रत्येक लोगो को `manifest.json` में SHA-256 हैश द्वारा ट्रैक किया जाता है। CI सिस्टम, `logos/` या `manifest.json` को प्रभावित करने वाले प्रत्येक पुश पर `brand manifest --check` कमांड चलाता है। किसी भी प्रकार की विसंगति - चाहे वह आकस्मिक ओवरराइट हो, छेड़छाड़ हो, या विचलन - बिल्ड को विफल कर देती है।
72
+
73
+ सुरक्षा नीति के लिए [SECURITY.md](SECURITY.md) देखें, और माइग्रेशन गाइड के लिए [docs/handbook.md](docs/handbook.md) देखें।
74
+
75
+ ## गोपनीयता
76
+
77
+ यह टूल कोई भी डेटा एकत्र नहीं करता है। सभी कार्य केवल स्थानीय फ़ाइल सिस्टम पर किए जाते हैं।
78
+
79
+ ## स्कोरकार्ड
80
+
81
+ | श्रेणी | स्कोर | टिप्पणियाँ |
82
+ |----------|-------|-------|
83
+ | A. सुरक्षा | 10/10 | SECURITY.md, SHA-256 अखंडता, कोई नेटवर्क नहीं, कोई डेटा संग्रह नहीं। |
84
+ | B. त्रुटि प्रबंधन | 8/10 | संरचित त्रुटियां, स्पष्ट कमांड-लाइन आउटपुट, एग्जिट कोड। |
85
+ | C. ऑपरेटर दस्तावेज़ | 10/10 | README, CHANGELOG, हैंडबुक, पूर्ण कमांड-लाइन दस्तावेज़। |
86
+ | D. वितरण स्वच्छता | 9/10 | CI अखंडता जांच, 29 परीक्षण, संस्करण संरेखित। |
87
+ | E. पहचान | 10/10 | लोगो, अनुवाद, लैंडिंग पृष्ठ, मेटाडेटा। |
88
+ | **Total** | **47/50** | |
89
+
90
+ ## लाइसेंस
91
+
92
+ [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/README.it.md CHANGED
@@ -2,54 +2,62 @@
2
2
  <a href="README.ja.md">日本語</a> | <a href="README.zh.md">中文</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.md">English</a> | <a href="README.pt-BR.md">Português (BR)</a>
3
3
  </p>
4
4
 
5
- <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
7
- </p>
5
+ <p align="center">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
+ </p>
8
+
9
+ <p align="center">
10
+ <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
+ <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
13
+ <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
14
+ </p>
8
15
 
9
- <p align="center">
10
- <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
12
- <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
13
- </p>
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
14
20
 
15
- Registro centralizzato delle risorse del marchio per l'organizzazione GitHub [mcp-tool-shop-org](https://github.com/mcp-tool-shop-org). Un repository contiene tutti i loghi. Ogni file README fa riferimento a questo repository. Aggiornare una volta, aggiornare ovunque.
21
+ ---
16
22
 
17
23
  ## Perché
18
24
 
19
- Quando ogni repository contiene una propria copia del logo, si verificano duplicazioni, discrepanze e incoerenze. Un cambiamento di immagine richiede di cercare in oltre 80 repository. Questo repository risolve questo problema: i loghi sono memorizzati qui, e i file README li richiamano tramite URL `raw.githubusercontent.com`.
25
+ Quando ogni repository contiene una propria copia del logo, si verificano duplicazioni, discrepanze e incoerenze. Un cambiamento di immagine coordinata significa dover cercare in oltre 100 repository. Questo repository risolve questo problema: i loghi sono conservati qui, e i file README li richiamano tramite URL `raw.githubusercontent.com`.
20
26
 
21
27
  ## Struttura
22
28
 
23
- ```
24
- logos/
25
- <slug>/
26
- readme.png # or readme.jpg — format preserved as-is
27
- manifest.json # SHA-256 integrity hashes for every asset
28
- docs/
29
- handbook.md # Lessons learned from migrating 80+ repos
30
- ```
29
+ ```
30
+ logos/
31
+ <slug>/
32
+ readme.png # or readme.jpg — format preserved as-is
33
+ manifest.json # SHA-256 integrity hashes for every asset
34
+ docs/
35
+ handbook.md # Lessons learned from migrating 100+ repos
36
+ ```
31
37
 
32
- 81 loghi distribuiti in 81 repository. I file PNG rimangono file PNG, i file JPEG rimangono file JPEG. Il formato è una decisione del marchio, non un obiettivo di compilazione.
38
+ Sono presenti 117 loghi in tutta l'organizzazione. I file PNG rimangono file PNG, i file JPEG rimangono file JPEG. Il formato è una decisione di branding, non un obiettivo di compilazione.
33
39
 
34
40
  ## Interfaccia a riga di comando (CLI)
35
41
 
36
- ```bash
37
- # Verify all logos match their manifest hashes
38
- brand verify
39
-
40
- # Regenerate manifest after adding/replacing a logo
41
- brand manifest
42
-
43
- # CI mode — fail if manifest is out of date
44
- brand manifest --check
45
-
46
- # Audit repos for broken refs, badge collisions, indentation traps
47
- brand audit --repos /path/to/clones
48
-
49
- # Migrate READMEs to point at brand repo (dry run first)
50
- brand migrate --repos /path/to/clones --dry-run
51
- brand migrate --repos /path/to/clones
52
- ```
42
+ ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
45
+ # Verify all logos match their manifest hashes
46
+ brand verify
47
+
48
+ # Regenerate manifest after adding/replacing a logo
49
+ brand manifest
50
+
51
+ # CI mode — fail if manifest is out of date
52
+ brand manifest --check
53
+
54
+ # Audit repos for broken refs, badge collisions, indentation traps
55
+ brand audit --repos /path/to/clones
56
+
57
+ # Migrate READMEs to point at brand repo (dry run first)
58
+ brand migrate --repos /path/to/clones --dry-run
59
+ brand migrate --repos /path/to/clones
60
+ ```
53
61
 
54
62
  ## Aggiungere un nuovo logo
55
63
 
@@ -62,8 +70,29 @@ brand migrate --repos /path/to/clones
62
70
 
63
71
  Ogni logo è tracciato tramite l'hash SHA-256 nel file `manifest.json`. Il sistema CI esegue `brand manifest --check` ad ogni commit che modifica i file in `logos/` o `manifest.json`. Qualsiasi discrepanza (sovrascrittura accidentale, manomissione, discrepanza) causa il fallimento della compilazione.
64
72
 
65
- Consultare [docs/handbook.md](docs/handbook.md) per maggiori dettagli: perché i collegamenti simbolici non funzionano, come i badge interferiscono con il rilevamento dei loghi, le trappole di rendering Markdown che compromettono i tag `<img>`, e il protocollo di sicurezza per la migrazione.
73
+ Consultare [SECURITY.md](SECURITY.md) per la politica di sicurezza completa e [docs/handbook.md](docs/handbook.md) per la guida alla migrazione.
74
+
75
+ ## Privacy
76
+
77
+ Questo strumento non raccoglie dati di telemetria. Tutte le operazioni avvengono esclusivamente sul file system locale.
78
+
79
+ ## Valutazione
80
+
81
+ | Categoria | Punteggio | Note |
82
+ |----------|-------|-------|
83
+ | A. Sicurezza | 10/10 | SECURITY.md, integrità SHA-256, nessuna connessione di rete, nessuna telemetria. |
84
+ | B. Gestione degli errori | 8/10 | Errori strutturati, output CLI chiaro, codici di uscita. |
85
+ | C. Documentazione per gli operatori | 10/10 | README, CHANGELOG, guida, documentazione completa CLI. |
86
+ | D. Qualità del codice | 9/10 | Controllo di integrità CI, 29 test, versione allineata. |
87
+ | E. Identità | 10/10 | Logo, traduzioni, pagina di presentazione, metadati. |
88
+ | **Total** | **47/50** | |
66
89
 
67
90
  ## Licenza
68
91
 
69
92
  [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/README.ja.md CHANGED
@@ -2,54 +2,62 @@
2
2
  <a href="README.md">English</a> | <a href="README.zh.md">中文</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
3
3
  </p>
4
4
 
5
- <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
7
- </p>
5
+ <p align="center">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
+ </p>
8
+
9
+ <p align="center">
10
+ <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
+ <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
13
+ <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
14
+ </p>
8
15
 
9
- <p align="center">
10
- <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
12
- <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
13
- </p>
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
14
20
 
15
- [mcp-tool-shop-org] GitHub組織向けの、ブランドアセットの一元管理レジストリです。このリポジトリには、すべてのロゴが格納されています。各READMEファイルは、このリポジトリを指しています。一度更新すれば、すべての場所で更新されます。
21
+ ---
16
22
 
17
23
  ## なぜか
18
24
 
19
- 各リポジトリが独自のロゴコピーを持っていると、重複、乖離、および不整合が発生します。ブランド変更を行うには、80以上のリポジトリを個別に確認する必要があります。このリポジトリはその問題を解決します。ロゴはここに保存され、READMEファイルは`raw.githubusercontent.com`のURLを通じてそれらを参照します。
25
+ 各リポジトリが独自のロゴのコピーを持っていると、重複、乖離、そして一貫性の欠如が生じます。ブランド変更を行うには、100件以上のリポジトリを調査する必要があります。このリポジトリは、その問題を解決します。ロゴはここに保存され、READMEファイルは`raw.githubusercontent.com`のURLを通じてそれらを参照します。
20
26
 
21
27
  ## 構造
22
28
 
23
- ```
24
- logos/
25
- <slug>/
26
- readme.png # or readme.jpg — format preserved as-is
27
- manifest.json # SHA-256 integrity hashes for every asset
28
- docs/
29
- handbook.md # Lessons learned from migrating 80+ repos
30
- ```
29
+ ```
30
+ logos/
31
+ <slug>/
32
+ readme.png # or readme.jpg — format preserved as-is
33
+ manifest.json # SHA-256 integrity hashes for every asset
34
+ docs/
35
+ handbook.md # Lessons learned from migrating 100+ repos
36
+ ```
31
37
 
32
- 81個のロゴが、81個のリポジトリに分散して保存されています。PNGファイルはPNGのまま、JPEGファイルはJPEGのままです。ファイル形式は、ビルドの対象ではなく、ブランド側の決定です。
38
+ 組織全体で117種類のロゴがあります。PNGファイルはPNGのまま、JPEGファイルはJPEGのままです。ファイル形式は、ビルドの対象ではなく、ブランドの決定事項です。
33
39
 
34
40
  ## CLI (コマンドラインインターフェース)
35
41
 
36
- ```bash
37
- # Verify all logos match their manifest hashes
38
- brand verify
39
-
40
- # Regenerate manifest after adding/replacing a logo
41
- brand manifest
42
-
43
- # CI mode — fail if manifest is out of date
44
- brand manifest --check
45
-
46
- # Audit repos for broken refs, badge collisions, indentation traps
47
- brand audit --repos /path/to/clones
48
-
49
- # Migrate READMEs to point at brand repo (dry run first)
50
- brand migrate --repos /path/to/clones --dry-run
51
- brand migrate --repos /path/to/clones
52
- ```
42
+ ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
45
+ # Verify all logos match their manifest hashes
46
+ brand verify
47
+
48
+ # Regenerate manifest after adding/replacing a logo
49
+ brand manifest
50
+
51
+ # CI mode — fail if manifest is out of date
52
+ brand manifest --check
53
+
54
+ # Audit repos for broken refs, badge collisions, indentation traps
55
+ brand audit --repos /path/to/clones
56
+
57
+ # Migrate READMEs to point at brand repo (dry run first)
58
+ brand migrate --repos /path/to/clones --dry-run
59
+ brand migrate --repos /path/to/clones
60
+ ```
53
61
 
54
62
  ## 新しいロゴの追加
55
63
 
@@ -62,8 +70,29 @@ brand migrate --repos /path/to/clones
62
70
 
63
71
  すべてのロゴは、`manifest.json`ファイル内のSHA-256ハッシュによって追跡されます。CIは、`logos/`または`manifest.json`に影響を与えるすべてのプッシュに対して、`brand manifest --check`コマンドを実行します。不整合(意図しない上書き、改ざん、乖離など)が発生した場合、ビルドは失敗します。
64
72
 
65
- 詳細については、[docs/handbook.md](docs/handbook.md)を参照してください。シンボリックリンクが機能しない理由、バッジがロゴ検出と競合する理由、`<img>`タグを壊すMarkdownレンダリングの問題、および移行の安全プロトコルについて説明されています。
73
+ セキュリティポリシーについては[SECURITY.md](SECURITY.md) を、移行に関するガイドについては[docs/handbook.md](docs/handbook.md) を参照してください。
74
+
75
+ ## プライバシー
76
+
77
+ このツールは、テレメトリーデータを収集しません。すべての操作はローカルファイルシステム上でのみ行われます。
78
+
79
+ ## 評価
80
+
81
+ | カテゴリ | 評価 | 備考 |
82
+ |----------|-------|-------|
83
+ | A. セキュリティ | 10/10 | SECURITY.md、SHA-256による整合性チェック、ネットワーク接続なし、テレメトリーデータ収集なし |
84
+ | B. エラー処理 | 8/10 | 構造化されたエラー、明確なCLI出力、終了コード |
85
+ | C. 運用ドキュメント | 10/10 | README、CHANGELOG、ハンドブック、完全なCLIドキュメント |
86
+ | D. リリースの品質 | 9/10 | CIによる整合性チェック、29個のテスト、バージョン管理との整合性 |
87
+ | E. 識別 | 10/10 | ロゴ、翻訳、ランディングページ、メタデータ |
88
+ | **Total** | **47/50** | |
66
89
 
67
90
  ## ライセンス
68
91
 
69
92
  [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/README.md CHANGED
@@ -3,21 +3,26 @@
3
3
  </p>
4
4
 
5
5
  <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
7
  </p>
8
8
 
9
9
  <p align="center">
10
10
  <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
11
  <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
13
13
  <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
14
14
  </p>
15
15
 
16
- Centralized brand asset registry for the [mcp-tool-shop-org](https://github.com/mcp-tool-shop-org) GitHub org. One repo holds every logo. Every README points here. Update once, update everywhere.
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
20
+
21
+ ---
17
22
 
18
23
  ## Why
19
24
 
20
- When every repo carries its own copy of the logo, you get duplication, drift, and inconsistency. A rebrand means hunting through 80+ repos. This repo fixes that — logos live here, READMEs reference them via `raw.githubusercontent.com` URLs.
25
+ When every repo carries its own copy of the logo, you get duplication, drift, and inconsistency. A rebrand means hunting through 100+ repos. This repo fixes that — logos live here, READMEs reference them via `raw.githubusercontent.com` URLs.
21
26
 
22
27
  ## Structure
23
28
 
@@ -27,14 +32,16 @@ logos/
27
32
  readme.png # or readme.jpg — format preserved as-is
28
33
  manifest.json # SHA-256 integrity hashes for every asset
29
34
  docs/
30
- handbook.md # Lessons learned from migrating 80+ repos
35
+ handbook.md # Lessons learned from migrating 100+ repos
31
36
  ```
32
37
 
33
- 81 logos across 81 repos. PNGs stay PNGs. JPEGs stay JPEGs. Format is a brand decision, not a build target.
38
+ 117 logos across the org. PNGs stay PNGs. JPEGs stay JPEGs. Format is a brand decision, not a build target.
34
39
 
35
40
  ## CLI
36
41
 
37
42
  ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
38
45
  # Verify all logos match their manifest hashes
39
46
  brand verify
40
47
 
@@ -63,8 +70,29 @@ brand migrate --repos /path/to/clones
63
70
 
64
71
  Every logo is tracked by SHA-256 hash in `manifest.json`. CI runs `brand manifest --check` on every push that touches `logos/` or `manifest.json`. Any mismatch — accidental overwrite, tampering, drift — fails the build.
65
72
 
66
- See [docs/handbook.md](docs/handbook.md) for the full story: why symlinks don't work, how badges collide with logo detection, the markdown rendering traps that break `<img>` tags, and the migration safety protocol.
73
+ See [SECURITY.md](SECURITY.md) for the full security policy and [docs/handbook.md](docs/handbook.md) for the migration handbook.
74
+
75
+ ## Privacy
76
+
77
+ This tool collects no telemetry. All operations are local filesystem only.
78
+
79
+ ## Scorecard
80
+
81
+ | Category | Score | Notes |
82
+ |----------|-------|-------|
83
+ | A. Security | 10/10 | SECURITY.md, SHA-256 integrity, no network, no telemetry |
84
+ | B. Error Handling | 8/10 | Structured errors, clear CLI output, exit codes |
85
+ | C. Operator Docs | 10/10 | README, CHANGELOG, handbook, full CLI docs |
86
+ | D. Shipping Hygiene | 9/10 | CI integrity check, 29 tests, version aligned |
87
+ | E. Identity | 10/10 | Logo, translations, landing page, metadata |
88
+ | **Total** | **47/50** | |
67
89
 
68
90
  ## License
69
91
 
70
92
  [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/README.pt-BR.md CHANGED
@@ -2,54 +2,62 @@
2
2
  <a href="README.ja.md">日本語</a> | <a href="README.zh.md">中文</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.md">English</a>
3
3
  </p>
4
4
 
5
- <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
7
- </p>
5
+ <p align="center">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
+ </p>
8
+
9
+ <p align="center">
10
+ <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
+ <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
13
+ <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
14
+ </p>
8
15
 
9
- <p align="center">
10
- <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
12
- <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
13
- </p>
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
14
20
 
15
- Registro centralizado de ativos da marca para a organização GitHub [mcp-tool-shop-org](https://github.com/mcp-tool-shop-org). Um repositório contém todos os logotipos. Cada arquivo README aponta para este repositório. Atualize uma vez e atualize em todos os lugares.
21
+ ---
16
22
 
17
23
  ## Por que?
18
24
 
19
- Quando cada repositório possui sua própria cópia do logotipo, você obtém duplicação, desvio e inconsistência. Uma mudança de marca significa procurar em mais de 80 repositórios. Este repositório resolve isso: os logotipos ficam aqui, e os arquivos README fazem referência a eles por meio de URLs `raw.githubusercontent.com`.
25
+ Quando cada repositório possui sua própria cópia do logotipo, isso resulta em duplicação, desvio e inconsistência. Uma mudança de marca exige a busca em mais de 100 repositórios. Este repositório resolve esse problema: os logotipos estão armazenados aqui, e os arquivos README fazem referência a eles por meio de URLs do tipo `raw.githubusercontent.com`.
20
26
 
21
27
  ## Estrutura
22
28
 
23
- ```
24
- logos/
25
- <slug>/
26
- readme.png # or readme.jpg — format preserved as-is
27
- manifest.json # SHA-256 integrity hashes for every asset
28
- docs/
29
- handbook.md # Lessons learned from migrating 80+ repos
30
- ```
29
+ ```
30
+ logos/
31
+ <slug>/
32
+ readme.png # or readme.jpg — format preserved as-is
33
+ manifest.json # SHA-256 integrity hashes for every asset
34
+ docs/
35
+ handbook.md # Lessons learned from migrating 100+ repos
36
+ ```
31
37
 
32
- 81 logotipos em 81 repositórios. Os arquivos PNG permanecem como PNGs. Os arquivos JPEG permanecem como JPEGs. O formato é uma decisão da marca, não um alvo de compilação.
38
+ Existem 117 logotipos em toda a organização. Os arquivos PNG permanecem como PNGs. Os arquivos JPEG permanecem como JPEGs. O formato é uma decisão de marca, não um alvo de compilação.
33
39
 
34
40
  ## Interface de Linha de Comando (CLI)
35
41
 
36
- ```bash
37
- # Verify all logos match their manifest hashes
38
- brand verify
39
-
40
- # Regenerate manifest after adding/replacing a logo
41
- brand manifest
42
-
43
- # CI mode — fail if manifest is out of date
44
- brand manifest --check
45
-
46
- # Audit repos for broken refs, badge collisions, indentation traps
47
- brand audit --repos /path/to/clones
48
-
49
- # Migrate READMEs to point at brand repo (dry run first)
50
- brand migrate --repos /path/to/clones --dry-run
51
- brand migrate --repos /path/to/clones
52
- ```
42
+ ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
45
+ # Verify all logos match their manifest hashes
46
+ brand verify
47
+
48
+ # Regenerate manifest after adding/replacing a logo
49
+ brand manifest
50
+
51
+ # CI mode — fail if manifest is out of date
52
+ brand manifest --check
53
+
54
+ # Audit repos for broken refs, badge collisions, indentation traps
55
+ brand audit --repos /path/to/clones
56
+
57
+ # Migrate READMEs to point at brand repo (dry run first)
58
+ brand migrate --repos /path/to/clones --dry-run
59
+ brand migrate --repos /path/to/clones
60
+ ```
53
61
 
54
62
  ## Adicionando um Novo Logotipo
55
63
 
@@ -62,8 +70,29 @@ brand migrate --repos /path/to/clones
62
70
 
63
71
  Cada logotipo é rastreado por um hash SHA-256 no `manifest.json`. O CI executa `brand manifest --check` em cada envio que afeta os arquivos `logos/` ou `manifest.json`. Qualquer incompatibilidade – sobrescrita acidental, adulteração, desvio – causa a falha da compilação.
64
72
 
65
- Consulte [docs/handbook.md](docs/handbook.md) para obter mais detalhes: por que os links simbólicos não funcionam, como os selos interferem na detecção de logotipos, as armadilhas de renderização de Markdown que quebram as tags `<img>`, e o protocolo de segurança para migração.
73
+ Consulte [SECURITY.md](SECURITY.md) para a política de segurança completa e [docs/handbook.md](docs/handbook.md) para o guia de migração.
74
+
75
+ ## Privacidade
76
+
77
+ Esta ferramenta não coleta dados de telemetria. Todas as operações são realizadas apenas no sistema de arquivos local.
78
+
79
+ ## Avaliação
80
+
81
+ | Categoria | Pontuação | Observações |
82
+ |----------|-------|-------|
83
+ | A. Segurança | 10/10 | SECURITY.md, integridade SHA-256, sem conexão de rede, sem telemetria. |
84
+ | B. Tratamento de Erros | 8/10 | Erros estruturados, saída clara da linha de comando, códigos de saída. |
85
+ | C. Documentação para Usuários | 10/10 | README, CHANGELOG, guia, documentação completa da linha de comando. |
86
+ | D. Qualidade do Código | 9/10 | Verificação de integridade no CI, 29 testes, versão alinhada. |
87
+ | E. Identidade | 10/10 | Logotipo, traduções, página inicial, metadados. |
88
+ | **Total** | **47/50** | |
66
89
 
67
90
  ## Licença
68
91
 
69
92
  [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/README.zh.md CHANGED
@@ -2,54 +2,62 @@
2
2
  <a href="README.ja.md">日本語</a> | <a href="README.md">English</a> | <a href="README.es.md">Español</a> | <a href="README.fr.md">Français</a> | <a href="README.hi.md">हिन्दी</a> | <a href="README.it.md">Italiano</a> | <a href="README.pt-BR.md">Português (BR)</a>
3
3
  </p>
4
4
 
5
- <p align="center">
6
- <img src="assets/logo.jpg" alt="Brand" width="400">
7
- </p>
5
+ <p align="center">
6
+ <img src="https://raw.githubusercontent.com/mcp-tool-shop-org/brand/main/assets/logo.jpg" alt="Brand" width="400">
7
+ </p>
8
+
9
+ <p align="center">
10
+ <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
+ <a href="https://www.npmjs.com/package/@mcptoolshop/brand"><img src="https://img.shields.io/npm/v/@mcptoolshop/brand" alt="npm"></a>
12
+ <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT License"></a>
13
+ <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
14
+ </p>
8
15
 
9
- <p align="center">
10
- <a href="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml"><img src="https://github.com/mcp-tool-shop-org/brand/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
11
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License: MIT"></a>
12
- <a href="https://mcp-tool-shop-org.github.io/brand/"><img src="https://img.shields.io/badge/Landing_Page-live-blue" alt="Landing Page"></a>
13
- </p>
16
+ <p align="center">
17
+ Centralized brand asset registry for the <a href="https://github.com/mcp-tool-shop-org">mcp-tool-shop-org</a> GitHub org.<br>
18
+ One repo holds every logo. Every README points here. Update once, update everywhere.
19
+ </p>
14
20
 
15
- 为 [mcp-tool-shop-org](https://github.com/mcp-tool-shop-org) GitHub 组织提供的集中式品牌资产注册库。一个仓库包含所有 logo。每个 README 文件都指向这里。只需更新一次,即可在所有地方同步更新。
21
+ ---
16
22
 
17
23
  ## 原因
18
24
 
19
- 当每个仓库都包含自己的 logo 副本时,就会出现重复、偏差和不一致的情况。品牌重塑意味着需要在 80 多个仓库中进行搜索。这个仓库解决了这个问题——所有 logo 都存储在这里,README 文件通过 `raw.githubusercontent.com` URL 链接到它们。
25
+ 当每个代码仓库都包含自己的Logo副本时,就会出现重复、偏差和不一致的情况。重新设计品牌意味着需要在100多个代码仓库中进行查找。这个代码仓库解决了这个问题——Logo文件存储在此处,README文件通过`raw.githubusercontent.com`链接引用它们。
20
26
 
21
27
  ## 结构
22
28
 
23
- ```
24
- logos/
25
- <slug>/
26
- readme.png # or readme.jpg — format preserved as-is
27
- manifest.json # SHA-256 integrity hashes for every asset
28
- docs/
29
- handbook.md # Lessons learned from migrating 80+ repos
30
- ```
29
+ ```
30
+ logos/
31
+ <slug>/
32
+ readme.png # or readme.jpg — format preserved as-is
33
+ manifest.json # SHA-256 integrity hashes for every asset
34
+ docs/
35
+ handbook.md # Lessons learned from migrating 100+ repos
36
+ ```
31
37
 
32
- 81 个仓库,每个仓库包含一个 logo。PNG 格式的 logo 保持 PNG 格式,JPEG 格式的 logo 保持 JPEG 格式。文件格式是品牌决策,而不是构建目标。
38
+ 组织内共有117个Logo。PNG格式的Logo保持为PNG格式,JPEG格式的Logo保持为JPEG格式。文件格式是品牌决策,而不是构建目标。
33
39
 
34
40
  ## 命令行工具 (CLI)
35
41
 
36
- ```bash
37
- # Verify all logos match their manifest hashes
38
- brand verify
39
-
40
- # Regenerate manifest after adding/replacing a logo
41
- brand manifest
42
-
43
- # CI mode — fail if manifest is out of date
44
- brand manifest --check
45
-
46
- # Audit repos for broken refs, badge collisions, indentation traps
47
- brand audit --repos /path/to/clones
48
-
49
- # Migrate READMEs to point at brand repo (dry run first)
50
- brand migrate --repos /path/to/clones --dry-run
51
- brand migrate --repos /path/to/clones
52
- ```
42
+ ```bash
43
+ npm install -g @mcptoolshop/brand
44
+
45
+ # Verify all logos match their manifest hashes
46
+ brand verify
47
+
48
+ # Regenerate manifest after adding/replacing a logo
49
+ brand manifest
50
+
51
+ # CI mode — fail if manifest is out of date
52
+ brand manifest --check
53
+
54
+ # Audit repos for broken refs, badge collisions, indentation traps
55
+ brand audit --repos /path/to/clones
56
+
57
+ # Migrate READMEs to point at brand repo (dry run first)
58
+ brand migrate --repos /path/to/clones --dry-run
59
+ brand migrate --repos /path/to/clones
60
+ ```
53
61
 
54
62
  ## 添加新的 logo
55
63
 
@@ -62,8 +70,29 @@ brand migrate --repos /path/to/clones
62
70
 
63
71
  每个 logo 都通过 SHA-256 哈希值在 `manifest.json` 文件中进行跟踪。CI 系统在每次涉及 `logos/` 目录或 `manifest.json` 文件的提交时,都会运行 `brand manifest --check` 命令。任何不匹配的情况——意外覆盖、篡改或偏差——都会导致构建失败。
64
72
 
65
- 请参阅 [docs/handbook.md](docs/handbook.md) 获取完整信息:为什么符号链接不可用,徽章如何与 logo 检测冲突,以及 markdown 渲染中可能导致 `<img>` 标签失效的陷阱,以及迁移的安全协议。
73
+ 请参阅[SECURITY.md](SECURITY.md)以获取完整的安全策略,以及[docs/handbook.md](docs/handbook.md)以获取迁移指南。
74
+
75
+ ## 隐私
76
+
77
+ 此工具不收集任何遥测数据。所有操作仅在本地文件系统中进行。
78
+
79
+ ## 评估指标
80
+
81
+ | 类别 | 得分 | 备注 |
82
+ |----------|-------|-------|
83
+ | A. 安全性 | 10/10 | SECURITY.md,SHA-256完整性校验,无网络连接,无遥测数据。 |
84
+ | B. 错误处理 | 8/10 | 结构化错误信息,清晰的命令行输出,退出码。 |
85
+ | C. 操作文档 | 10/10 | README文件,CHANGELOG文件,操作手册,完整的命令行文档。 |
86
+ | D. 发布质量 | 9/10 | CI集成完整性检查,29个测试用例,版本对齐。 |
87
+ | E. 身份标识 | 10/10 | Logo,翻译文件,着陆页,元数据。 |
88
+ | **Total** | **47/50** | |
66
89
 
67
90
  ## 许可证
68
91
 
69
92
  [MIT](LICENSE)
93
+
94
+ ---
95
+
96
+ <p align="center">
97
+ Built by <a href="https://mcp-tool-shop.github.io/">MCP Tool Shop</a>
98
+ </p>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mcptoolshop/brand",
3
- "version": "0.1.2",
3
+ "version": "1.0.0",
4
4
  "description": "Centralized brand asset management — migration, audit, and integrity verification for GitHub orgs",
5
5
  "type": "module",
6
6
  "bin": {