RRepoGEO

REPOGEO REPORT · LITE

typedgrammar/typed-japanese

Default branch main · commit 8b0988b7 · scanned 5/22/2026, 2:15:34 AM

GitHub: 1,922 stars · 22 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

2 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface typedgrammar/typed-japanese, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition the README's opening to emphasize type-level Japanese grammar enforcement

    Why:

    CURRENT
    Typed Japanese is a TypeScript type-level library that enables the expression of complete Japanese sentences through the type system.
    COPY-PASTE FIX
    Typed Japanese is a **TypeScript type-level library for compile-time Japanese grammar enforcement and verification**, enabling the expression of complete Japanese sentences through the type system.
  • mediumreadme#2
    Add a dedicated 'Why Typed Japanese?' section to the README

    Why:

    COPY-PASTE FIX
    Add a new section titled 'Why Typed Japanese?' or 'What Problem Does This Solve?' that explicitly contrasts its type-driven grammar enforcement with traditional Japanese NLP tools (like MeCab, Juman++, SudachiPy) and general type-level programming. Emphasize its role in compile-time verification and language learning.
  • lowtopics#3
    Add more specific topics to reinforce the unique combination

    Why:

    CURRENT
    computational-linguistics, dsl, grammar, japanese, japanese-grammar, language-learning, language-verification, nlp, type-level-programming, type-system, typescript, typescript-types
    COPY-PASTE FIX
    Add `type-safe-grammar`, `grammar-dsl`, `compile-time-verification` to the existing topics.

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface typedgrammar/typed-japanese
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
microsoft/TypeScript
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. microsoft/TypeScript · recommended 1×
  2. takuyaa/kuromoji.js · recommended 1×
  3. WorksApplications/Sudachi.js · recommended 1×
  4. Jisho API · recommended 1×
  5. Shapeless · recommended 1×
  • CATEGORY QUERY
    How to use TypeScript types to enforce Japanese grammar rules?
    you: not recommended
    AI recommended (in order):
    1. TypeScript (microsoft/TypeScript)
    2. Kuromoji.js (takuyaa/kuromoji.js)
    3. Sudachi.js (WorksApplications/Sudachi.js)
    4. Jisho API

    AI recommended 4 alternatives but never named typedgrammar/typed-japanese. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a type-level library for verifying Japanese sentence structure programmatically.
    you: not recommended
    AI recommended (in order):
    1. Shapeless
    2. Agda
    3. Idris
    4. GHC Extensions
    5. Haskell
    6. Common Lisp
    7. Racket
    8. TypeScript

    AI recommended 8 alternatives but never named typedgrammar/typed-japanese. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of typedgrammar/typed-japanese?
    pass
    AI named typedgrammar/typed-japanese explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts typedgrammar/typed-japanese in production, what risks or prerequisites should they evaluate first?
    pass
    AI named typedgrammar/typed-japanese explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo typedgrammar/typed-japanese solve, and who is the primary audience?
    pass
    AI named typedgrammar/typed-japanese explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of typedgrammar/typed-japanese. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/typedgrammar/typed-japanese.svg)](https://repogeo.com/en/r/typedgrammar/typed-japanese)
HTML
<a href="https://repogeo.com/en/r/typedgrammar/typed-japanese"><img src="https://repogeo.com/badge/typedgrammar/typed-japanese.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

typedgrammar/typed-japanese — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite