nuwave/lighthouse

A framework for serving GraphQL from Laravel

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 19th, 2026
Created on May 29th, 2016
Open Issues & Pull Requests: 137 (+0)
GitHub issues: Enabled
Number of forks: 468
Total Stargazers: 3,498 (+0)
Total Subscribers: 34 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 26
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,083 days
Stale 30+ days: 25
Stale 90+ days: 23

Recent activity

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

Top labels

  • enhancement (19)
  • discussion (11)
  • bug (9)
  • needs reproduction (4)
  • performance (2)
  • question (2)
  • docs (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Lighthouse is a framework for serving GraphQL from Laravel.

Lighthouse solves the problem of integrating GraphQL into Laravel applications by combining patterns from both the GraphQL and Laravel ecosystems. It handles common GraphQL tasks automatically while preserving flexibility for custom requirements. The framework integrates directly with Laravel, allowing developers to define GraphQL schemas and resolvers within their existing Laravel codebase.

Lighthouse suits Laravel developers building GraphQL APIs who want a tightly integrated solution rather than a standalone GraphQL server. It works well for projects where the GraphQL layer needs to interact closely with Laravel's models, middleware, and service container. The tool is appropriate for teams already invested in Laravel and seeking to add GraphQL capabilities without adopting a separate framework ecosystem.

The project maintains a changelog documenting all notable changes and provides an upgrade guide for major version transitions. Lighthouse follows semantic versioning with only the current major version receiving new features and bugfixes. Code elements marked with the @api annotation remain compatible across minor versions, though other internal code may change. The project has established contribution guidelines and uses GitHub discussions for community questions and feature proposals.