RRepoGEO

REPOGEO REPORT · LITE

567-labs/instructor-js

Default branch main · commit 868ef8c1 · scanned 6/6/2026, 10:46:50 AM

GitHub: 795 stars · 73 forks

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 567-labs/instructor-js, 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 README opening to emphasize LLM-specific guarantees

    Why:

    CURRENT
    _Structured extraction in Typescript, powered by llms, designed for simplicity, transparency, and control._
    COPY-PASTE FIX
    _Guaranteed type-safe structured extraction from LLMs in TypeScript, powered by OpenAI's function calling API and Zod, with automatic re-extraction/retrying for invalid outputs._
  • mediumtopics#2
    Add more specific LLM-related topics

    Why:

    CURRENT
    llm, openai, zod
    COPY-PASTE FIX
    llm, openai, zod, function-calling, structured-output, type-safety, ai-extraction, typescript
  • lowreadme#3
    Add a 'Comparison' section to the README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, e.g., '## Comparison to Zod/TypeBox/etc.', explaining why Instructor-JS is different and when to use it over a standalone schema library.

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 567-labs/instructor-js
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Zod
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. Zod · recommended 1×
  2. TypeBox · recommended 1×
  3. Valibot · recommended 1×
  4. AJV · recommended 1×
  5. Superstruct · recommended 1×
  • CATEGORY QUERY
    How to extract structured data from LLM responses using TypeScript?
    you: not recommended
    AI recommended (in order):
    1. Zod
    2. TypeBox
    3. Valibot
    4. AJV
    5. Superstruct
    6. Yup
    7. io-ts

    AI recommended 7 alternatives but never named 567-labs/instructor-js. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Library for enforcing output schemas and type safety from large language models?
    you: not recommended
    AI recommended (in order):
    1. Pydantic
    2. instructor
    3. JSON Schema
    4. jsonschema
    5. TypeChat
    6. Guardrails AI
    7. LangChain's Output Parsers
    8. PydanticOutputParser
    9. StructuredOutputParser
    10. LlamaIndex's PydanticProgram

    AI recommended 10 alternatives but never named 567-labs/instructor-js. 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 567-labs/instructor-js?
    pass
    AI named 567-labs/instructor-js explicitly

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

  • If a team adopts 567-labs/instructor-js in production, what risks or prerequisites should they evaluate first?
    pass
    AI named 567-labs/instructor-js 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 567-labs/instructor-js solve, and who is the primary audience?
    pass
    AI named 567-labs/instructor-js 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 567-labs/instructor-js. 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/567-labs/instructor-js.svg)](https://repogeo.com/en/r/567-labs/instructor-js)
HTML
<a href="https://repogeo.com/en/r/567-labs/instructor-js"><img src="https://repogeo.com/badge/567-labs/instructor-js.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

567-labs/instructor-js — 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