[Integrations](https://spiral.ai/integrations) › [VS Code](https://spiral.ai/integrations/vscode) › [GitHub repository details](https://spiral.ai/integrations/vscode/github-repository-details)

# How to Use GitHub repository details in VS Code

Fetch repository metadata such as stars, forks, language, license, activity dates, and archive status. Use it for an initial project assessment before reading releases, files, or individual issues.

|  |  |
| --- | --- |
| Model | GitHub repository details |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with GitHub repository details in VS Code

- Use GitHub repository details to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from GitHub repository details and tell me what changed since last week.
- Check GitHub repository details and summarize what you find in three bullet points.
- Pull the newest data from GitHub repository details and give me the result as a table.
- Check GitHub repository details every morning and tell me only when something changed.

## How to set up GitHub repository details in VS Code

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add the hosted server**: Use Add to VS Code on the console's Agents & MCP page, or run:

```bash
code --add-mcp '{"name":"spiral","type":"http","url":"https://api.spiral.ai/mcp"}'
```

2. **Sign in**: VS Code asks you to sign in when it first starts the server: sign in to Spiral and click Authorize. No API key. Run MCP: List Servers from the Command Palette to check that Spiral is running.

### Use the Spiral skill

1. **Send VS Code this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run GitHub repository details**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "github-com/repositories/repo",
    "input": {
      "repo": "<repo>"
    }
  }'
```

Then paste one of the prompts above: VS Code finds GitHub repository details on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/vscode

## GitHub repository details tools and prices

- [GitHub · Repo](https://spiral.ai/tools/alexandria/github-com/repositories/repo) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| url |  | — | HTTPS github.com/{owner}/{name} URL; deeper paths (issues, tree, ...) are accepted and reduced to the repository. Provide exactly one of repo or url. Pattern: ^(?:https?://)?(?:www\.)?github\.com/[A-Za-z0-9-]{1,39}/[A-Za-z0-9._-]{1,100}(?:[/?#].*)?$. |
| repo |  | — | Repository as `owner/name`, for example `firecrawl/firecrawl`. Provide exactly one of repo or url. Pattern: ^@?/?[A-Za-z0-9](?:[A-Za-z0-9-]{0,37}[A-Za-z0-9])?/[A-Za-z0-9._-]{1,100}(?:\.git)?/?$. |

## What can you do with GitHub repository details in VS Code?

Build a dependency review beside the code using GitHub files, release notes, issue evidence, and package advisories. A coding agent can compare those records with the project's manifests and turn the findings into proposed changes.

### Review a dependency before adoption

Build an adoption brief covering repository status, contribution concentration, license text, issue categories and totals, release history, and reported vulnerability or malware concerns for the exact packages under consideration.

### Prepare a dependency upgrade review

Compare the installed version with published releases, read migration files and known issue reports, and check relevant advisories. Include project status and contribution concentration when deciding how much upstream support to expect.

### Maintain a package security watch

Check a defined package list for malware reports and known advisory changes, then compare repository status, manifests, and published releases with the previous review. Produce a change report with links to the supporting records.

### Assess upstream maintenance

Compare archive status, contribution concentration, release dates, issue categories, and backlog totals across candidate repositories. Read representative issue reports to explain the numbers.

### Plan an open source contribution

Read contribution instructions, discover the repository's actual labels, and inspect suitable issues alongside backlog totals. Use project status and contribution distribution to understand the project's context before proposing work.

### Compare migration destinations

Compare two public projects using their README files, repository metadata, contribution distribution, release notes, and issue evidence. Summarize which documented limitations matter for the planned migration.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All VS Code guides](https://spiral.ai/integrations/vscode)

## GitHub repository details in other agents

- [Amp](https://spiral.ai/integrations/amp/github-repository-details)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/github-repository-details)
- [Claude](https://spiral.ai/integrations/claude-desktop/github-repository-details)
- [Claude Code](https://spiral.ai/integrations/claude-code/github-repository-details)
- [Cline](https://spiral.ai/integrations/cline/github-repository-details)
- [Codex](https://spiral.ai/integrations/codex/github-repository-details)
- [Cursor](https://spiral.ai/integrations/cursor/github-repository-details)
- [Devin](https://spiral.ai/integrations/devin/github-repository-details)
- [dots](https://spiral.ai/integrations/dots/github-repository-details)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/github-repository-details)
- [Gemini](https://spiral.ai/integrations/gemini/github-repository-details)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/github-repository-details)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/github-repository-details)
- [goose](https://spiral.ai/integrations/goose/github-repository-details)
- [Grok](https://spiral.ai/integrations/grok/github-repository-details)
- [Grok Build](https://spiral.ai/integrations/grok-build/github-repository-details)
- [Hermes](https://spiral.ai/integrations/hermes/github-repository-details)
- [Instinct](https://spiral.ai/integrations/instinct/github-repository-details)
- [Manus](https://spiral.ai/integrations/manus/github-repository-details)
- [Muse](https://spiral.ai/integrations/muse/github-repository-details)
- [Muse Code](https://spiral.ai/integrations/muse-code/github-repository-details)
- [n8n](https://spiral.ai/integrations/n8n/github-repository-details)
- [Notion](https://spiral.ai/integrations/notion/github-repository-details)
- [OpenClaw](https://spiral.ai/integrations/openclaw/github-repository-details)
- [opencode](https://spiral.ai/integrations/opencode/github-repository-details)
- [Perplexity](https://spiral.ai/integrations/perplexity/github-repository-details)
- [Raycast](https://spiral.ai/integrations/raycast/github-repository-details)
- [Windsurf](https://spiral.ai/integrations/windsurf/github-repository-details)
- [Zapier](https://spiral.ai/integrations/zapier/github-repository-details)

## More VS Code guides

- [GitHub repository contributors](https://spiral.ai/integrations/vscode/github-repository-contributors)
- [GitHub repository file](https://spiral.ai/integrations/vscode/github-repository-file)
- [GitHub release history](https://spiral.ai/integrations/vscode/github-release-history)
- [GitHub repository issue counts](https://spiral.ai/integrations/vscode/github-repository-issue-counts)
- [GitHub public account profile](https://spiral.ai/integrations/vscode/github-public-account-profile)
- [GitHub repository issues](https://spiral.ai/integrations/vscode/github-repository-issues)

## Questions about GitHub repository details in VS Code

**Can VS Code use GitHub repository details?**

Yes. Add Spiral to VS Code as an MCP server, and VS Code can find and run GitHub repository details like any built-in tool.

**How much does GitHub repository details cost in VS Code?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your VS Code plan is separate.

**Do I need an Alexandria account to use GitHub repository details in VS Code?**

No. Spiral runs GitHub repository details on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up GitHub repository details in VS Code?**

About two minutes: add the hosted server, then sign in.

**Does VS Code wait while GitHub repository details runs?**

GitHub repository details runs in the background. VS Code starts the run, checks on it and gives you the json when it's ready.

**Can I reuse anything that is public on GitHub?**

Public visibility alone does not grant unrestricted reuse. GitHub says that without a license, default copyright restrictions apply to source code; its Advisory Database has a separate CC BY 4.0 license.

**How current is GitHub's data?**

Freshness depends on the record. Contributor results can be a few hours old because GitHub caches them, while a file selected by branch can change whenever new commits arrive.

**Does a GitHub release history include every version tag?**

No. GitHub excludes Git tags that have no associated release, and its latest-release lookup excludes prereleases and drafts.

**Do GitHub issues include pull requests?**

GitHub's underlying issue responses can contain both, with pull requests identified separately. An issue-only backlog should exclude pull requests before its totals are compared.

**Where do GitHub's malware reports come from?**

GitHub automatically publishes malware advisories from the npm security team and the OpenSSF Malicious Packages repository. These reports concern malicious packages and are separate from ordinary vulnerability advisories.

