[Integrations](https://spiral.ai/integrations) › [Muse](https://spiral.ai/integrations/muse) › [GitHub release history](https://spiral.ai/integrations/muse/github-release-history)

# How to Use GitHub release history in Muse

Fetch published releases with tags, notes, dates, and assets, including prereleases. Use the history to compare upgrade paths; Git tags without an associated release are absent.

|  |  |
| --- | --- |
| Model | GitHub release history |
| Available through | Alexandria |
| Category | E-commerce |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with GitHub release history in Muse

- Use GitHub release history for nodejs/node to summarize the release notes from the ten most recent published releases, identifying prereleases.
- Use GitHub release history to look this up and give me the result as a table.
- Pull the latest numbers from GitHub release history and tell me what changed since last week.
- Check GitHub release history and summarize what you find in three bullet points.
- Pull the newest data from GitHub release history and give me the result as a table.

## How to set up GitHub release history in Muse

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

### Use the Muse connector

1. **Create an API key**: Create one under API keys in the Spiral console.

2. **Send Muse this message**: Muse reads Spiral's skill and asks for an API key.

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

3. **Give Muse the key**: Paste the key when Muse asks for it, never in the chat itself.

### Use the Spiral skill

1. **Send Muse 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 release history**: 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/releases",
    "input": {
      "repo": "<repo>"
    }
  }'
```

Then paste one of the prompts above: Muse finds GitHub release history on Spiral, shows the price and runs it.

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

## GitHub release history tools and prices

- [GitHub · Releases](https://spiral.ai/tools/alexandria/github-com/repositories/releases) (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}(?:[/?#].*)?$. |
| page | 1 to 1000 | 1 | 1-based page; has_next in the response says whether page+1 exists. |
| 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)?/?$. |
| per_page | 1 to 100 | 30 | Records per page. |

## What can you do with GitHub release history in Muse?

Get a project or package assessment grounded in GitHub's public records. A chat app can explain release changes, reported problems, repository activity, and advisory findings with links to the evidence.

### 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.

### Investigate a reported package incident

Read the advisory and affected package ranges, compare release notes and manifests, then inspect related issue categories, reports, and totals. Keep a documented vulnerability fix separate from a malicious-package report.

### 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.

### 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.

### Write a vulnerability remediation brief

Explain a known CVE using its affected ranges, upstream files, and release notes. Check malicious-package reports separately and identify whether the evidence supports an upgrade or removing the package.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Muse guides](https://spiral.ai/integrations/muse)

## GitHub release history in other agents

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

## More Muse guides

- [GitHub public account profile](https://spiral.ai/integrations/muse/github-public-account-profile)
- [GitHub repository contributors](https://spiral.ai/integrations/muse/github-repository-contributors)
- [GitHub malware advisories](https://spiral.ai/integrations/muse/github-malware-advisories)
- [GitHub repository details](https://spiral.ai/integrations/muse/github-repository-details)
- [GitHub latest release](https://spiral.ai/integrations/muse/github-latest-release)
- [GitHub repository file](https://spiral.ai/integrations/muse/github-repository-file)

## Questions about GitHub release history in Muse

**Can Muse use GitHub release history?**

Yes. Add Spiral to Muse as an MCP server, and Muse can find and run GitHub release history like any built-in tool.

**How much does GitHub release history cost in Muse?**

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

**Do I need an Alexandria account to use GitHub release history in Muse?**

You need no Alexandria account. Muse uses one Spiral API key for every tool, and Spiral runs GitHub release history on its own Alexandria account.

**How long does it take to set up GitHub release history in Muse?**

About two minutes: create an API key, then send Muse this message, then give Muse the key.

**Does Muse wait while GitHub release history runs?**

GitHub release history runs in the background. Muse 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.

