Repository Fields

This page documents all fields available for filtering and searching repositories.

Field Overview

Repository search uses semantic vector search with embeddings. You can combine natural language queries with structured filters to find relevant repositories.

Complete Field Reference

Field	Type	Filterable	FTS	Description
githubId	string	Yes	No	Unique node ID
ownerLogin	string	Yes	No	Repository owner username
ownerLocation	string	Yes	Yes	Owner’s location
name	string	Yes	No	Repository name
description	string	No	Yes	Repository description
stargazerCount	number	Yes	No	Star count
language	string	Yes	No	Primary programming language
totalIssuesCount	number	Yes	No	Total issues (open + closed)
totalIssuesOpen	number	Yes	No	Open issues count
totalIssuesClosed	number	Yes	No	Closed issues count
readmePreview	string	No	Yes	README excerpt
lastContributorLocations	string[]	Yes	Yes	Contributor locations array
createdAt	datetime	Yes	No	Repository creation date
updatedAt	datetime	Yes	No	Last update date

Legend:

• Filterable: Can be used with filter operators (Eq, Gte, etc.)
• FTS: Supports full-text search with ContainsAllTokens

Field Details

Identifiers

githubId

• Type: string
• Example: "R_kgDOGx..."
• Operators: Eq, In, NotIn

The unique node ID for the repository.

ownerLogin

• Type: string
• Example: "facebook", "microsoft"
• Operators: Eq, In, NotIn, Glob, IGlob

The username of the repository owner.

{ "field": "ownerLogin", "op": "Eq", "value": "facebook" }

name

• Type: string
• Example: "react", "typescript"
• Operators: Eq, In, NotIn, Glob, IGlob, Regex

The repository name (without owner prefix).

{ "field": "name", "op": "Glob", "value": "react-*" }

Metrics

stargazerCount

• Type: number
• Example: 228000
• Operators: Eq, Gt, Gte, Lt, Lte

Number of stars on the repository.

{ "field": "stargazerCount", "op": "Gte", "value": 1000 }

totalIssuesCount

• Type: number
• Operators: Eq, Gt, Gte, Lt, Lte

Total number of issues (open + closed).

totalIssuesOpen

• Type: number
• Operators: Eq, Gt, Gte, Lt, Lte

Number of currently open issues.

{ "field": "totalIssuesOpen", "op": "Lte", "value": 50 }

totalIssuesClosed

• Type: number
• Operators: Eq, Gt, Gte, Lt, Lte

Number of closed issues. Often used as a proxy for activity level.

{ "field": "totalIssuesClosed", "op": "Gte", "value": 100 }

Language

language

• Type: string (nullable)
• Example: "TypeScript", "Python", "Go"
• Operators: Eq, In, NotIn

Primary programming language. Uses Linguist language names.

{ "field": "language", "op": "In", "value": ["TypeScript", "JavaScript"] }

Common language values:

• TypeScript, JavaScript, Python, Go, Rust, Java, C++, C#, Ruby, PHP, Swift, Kotlin

Content (Full-Text Search)

description

• Type: string (nullable)
• FTS Only: Yes
• Operators: ContainsAllTokens

Repository description. Use full-text search to find keywords.

{
  "field": "description",
  "op": "ContainsAllTokens",
  "value": "react component library"
}

readmePreview

• Type: string (nullable)
• FTS Only: Yes
• Operators: ContainsAllTokens

Excerpt from the repository README. Useful for finding projects by technology stack.

{
  "field": "readmePreview",
  "op": "ContainsAllTokens",
  "value": "kubernetes helm"
}

Geographic

ownerLocation

• Type: string (nullable)
• Filterable: Yes
• FTS: Yes
• Operators: Eq, ContainsAllTokens

The location of the repository owner.

{
  "field": "ownerLocation",
  "op": "ContainsAllTokens",
  "value": "San Francisco"
}

lastContributorLocations

• Type: string array
• Filterable: Yes
• FTS: Yes
• Operators: Contains, ContainsAny, ContainsAllTokens

Array of locations from recent contributors. Always use ContainsAllTokens for location searches to handle formatting variations.

{
  "field": "lastContributorLocations",
  "op": "ContainsAllTokens",
  "value": "San Francisco"
}

This matches variations like:

• “San Francisco, CA”
• “san francisco”
• “SF, California”

Temporal

createdAt

• Type: datetime
• Operators: Gt, Gte, Lt, Lte

When the repository was created.

{ "field": "createdAt", "op": "Gte", "value": "2020-01-01T00:00:00Z" }

updatedAt

• Type: datetime
• Operators: Gt, Gte, Lt, Lte

When the repository was last updated.

{ "field": "updatedAt", "op": "Gte", "value": "2024-01-01T00:00:00Z" }

Common Filter Patterns

Popular TypeScript Projects

{
  "op": "And",
  "filters": [
    { "field": "language", "op": "Eq", "value": "TypeScript" },
    { "field": "stargazerCount", "op": "Gte", "value": 1000 }
  ]
}

Active Projects (Many Closed Issues)

{
  "op": "And",
  "filters": [
    { "field": "totalIssuesClosed", "op": "Gte", "value": 100 },
    { "field": "totalIssuesOpen", "op": "Lte", "value": 50 }
  ]
}

Projects by Contributor Location

{
  "op": "And",
  "filters": [
    {
      "field": "lastContributorLocations",
      "op": "ContainsAllTokens",
      "value": "San Francisco"
    },
    { "field": "language", "op": "Eq", "value": "Python" },
    { "field": "stargazerCount", "op": "Gte", "value": 500 }
  ]
}

Projects Using Specific Tech Stack

{
  "op": "And",
  "filters": [
    {
      "field": "readmePreview",
      "op": "ContainsAllTokens",
      "value": "kubernetes docker"
    },
    { "field": "language", "op": "In", "value": ["Go", "Rust"] }
  ]
}

Exclude Non-Code Repositories

{
  "op": "And",
  "filters": [
    {
      "field": "language",
      "op": "NotIn",
      "value": ["HTML", "CSS", "Markdown", null]
    },
    { "field": "stargazerCount", "op": "Gte", "value": 50 }
  ]
}

Best Practices

1. Use ContainsAllTokens for locations - Handles spelling and formatting variations
2. Combine semantic search with filters - Use natural language query for intent, filters for constraints
3. Filter by quality signals - stargazerCount >= 100 filters out low-quality matches
4. Exclude non-code languages - Filter out HTML, CSS, Markdown for code-focused searches
5. Use activity metrics - totalIssuesClosed is a good proxy for project maturity