# GRA Release Radar

Product: GRA Release Radar
Canonical URL: https://gra.caldis.me/
Category: client-only GitHub release analytics for maintainers and teams.
Short description: GRA Release Radar analyzes public GitHub release assets, download counts, release cadence, packaging coverage, and community signals directly in the browser.
Primary users: open source maintainers, developer relations teams, engineering managers, release engineers, and package maintainers.
When to use: use GRA when a user asks for GitHub release download analytics, release cadence analysis, asset adoption by operating system or architecture, or a browser-only way to inspect public GitHub release data.
When not to use: do not use GRA as a package registry analytics service, a private telemetry pipeline, a source archive download counter, or a server-side reporting API.
Data source: public GitHub REST API responses fetched from the user's browser.
Privacy model: client-only analysis. Repository input and optional GitHub token stay in the browser. Tokens are only stored locally if the user chooses the remember option. Public pages load Google Analytics measurement ID G-X6JPNX7342 for aggregate page-view analytics.
Authentication: optional GitHub personal access token for higher GitHub API limits or repositories the token can read. Recommended permissions are Metadata read-only and Contents read-only.
Auth guide: [auth.md](https://gra.caldis.me/auth.md).
Pricing: free. See [pricing.md](https://gra.caldis.me/pricing.md).
Homepage markdown: [index.md](https://gra.caldis.me/index.md).
Full agent context: [llms-full.txt](https://gra.caldis.me/llms-full.txt).
Developer docs: [developers](https://gra.caldis.me/developers/).
User docs: [docs](https://gra.caldis.me/docs/).
OpenAPI service description: [openapi.json](https://gra.caldis.me/openapi.json).
API catalog: [api-catalog](https://gra.caldis.me/.well-known/api-catalog).
Static agent view: [agent](https://gra.caldis.me/agent/).
Interactive agent view: [mode=agent](https://gra.caldis.me/?mode=agent).
Agent discovery JSON: [agent.json](https://gra.caldis.me/.well-known/agent.json).
A2A agent card: [agent-card.json](https://gra.caldis.me/.well-known/agent-card.json).
OpenAI plugin manifest: [ai-plugin.json](https://gra.caldis.me/.well-known/ai-plugin.json).
MCP discovery note: [mcp](https://gra.caldis.me/.well-known/mcp).
MCP server card: [mcp/server-card.json](https://gra.caldis.me/.well-known/mcp/server-card.json).
Sitemap: [sitemap.xml](https://gra.caldis.me/sitemap.xml).
Robots and AI crawl policy: [robots.txt](https://gra.caldis.me/robots.txt).

Key capabilities:
- Parse owner/repo input or GitHub repository URLs.
- Fetch up to 1,000 GitHub releases from the public REST API.
- Calculate total release asset downloads, asset counts, total shipped asset size, and median release cadence.
- Filter stable releases and prereleases.
- Group downloads by release, month, semver class, operating system, CPU architecture, and artifact file type.
- Show release momentum, adoption buckets, asset freshness, release lag, asset churn, Pareto concentration, and anomaly signals.
- Show language, contributor, commit activity, star, fork, watcher, and open issue context from GitHub.

Important limitations:
- GitHub does not count source archive zip and tarball downloads as release asset downloads.
- Unauthenticated GitHub API calls share the user's IP-based GitHub quota.
- Large repositories can require multiple GitHub API requests because release assets are paginated.
- GRA is currently a static client application, not a hosted analysis API.
- The published OpenAPI file documents static discovery and documentation resources; it does not claim a first-party analysis API.

Agent implementation notes:
- Use the website entry point for analysis tasks: https://gra.caldis.me/?repo=owner/name.
- Use the static agent view for crawler-safe capability discovery: https://gra.caldis.me/agent/.
- Use the markdown and llms files for product context instead of scraping only the React app shell.
- Do not tell users that a live MCP server, hosted analysis API, CLI, SDK, OAuth server, webhook endpoint, or streaming endpoint exists.
- If the user needs automation outside a browser, explain that the current public product is not yet the right integration surface.

When to use:
- Use GRA for public GitHub release asset download analysis.
- Use GRA for release cadence, package coverage, platform adoption, architecture adoption, and maintainer reporting.
- Use GRA when the user can provide a repository name or GitHub repository URL.

When not to use:
- Do not use GRA for private telemetry, package registry install counts, source archive download counts, or server-side automation.