absinthe-graphql/absinthe

The GraphQL toolkit for Elixir

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 53 minutes ago
Added to GitGenius on September 15th, 2026
Created on October 17th, 2015
Open Issues & Pull Requests: 69 (+0)
GitHub issues: Enabled
Number of forks: 560
Total Stargazers: 4,402 (+0)
Total Subscribers: 69 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.5 hours
Mean response time: 123.2 days
90th percentile: 440.5 days
Tracked items: 32

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 1,033 days
Stale 30+ days: 16
Stale 90+ days: 14

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 2

Top labels

  • Kind:Feature (2)
  • Kind:Discussion (1)

Most active issues this week

Detailed Description

Absinthe is a GraphQL toolkit for Elixir that enables developers to build GraphQL APIs in Elixir applications.

Absinthe solves the problem of integrating GraphQL into Elixir projects by providing a complete implementation of the GraphQL specification. The toolkit allows developers to define schemas, resolvers, and queries using Elixir's syntax and idioms. It handles the parsing, validation, and execution of GraphQL queries against defined schemas, bridging the gap between client applications expecting GraphQL interfaces and Elixir backend services.

Absinthe suits teams building GraphQL APIs with Elixir, particularly those using the Phoenix web framework or other Elixir applications that need to expose data through a GraphQL interface. It is appropriate for projects ranging from small services to larger applications requiring complex schema definitions and nested query resolution. Developers familiar with Elixir's functional programming model and pattern matching will find the toolkit's approach natural, as it leverages these language features for schema definition and query handling.

The project maintains steady development activity with regular commits addressing bug fixes, feature additions, and maintenance tasks. The codebase shows consistent attention to test coverage and code quality. The maintainers actively engage with issues and pull requests, indicating ongoing stewardship of the project. Documentation is kept current alongside code changes, supporting users implementing the toolkit in their applications.