Our take
Inactiveno commits in over a year- Activity
- 19
- Community
- 46
- Issues
- 21
- Pull requests
- 20
+9 stars in the last 30 days
This is a wide-ranging ecosystem directory with useful discovery value, but its inactive maintenance and concentrated contributions make it better for finding leads than relying on as a current, verified catalog.
Good fit if
- You already work with Lua and want a categorized starting point for finding packages or related resources.
- You can independently check the maintenance, compatibility, and suitability of the linked projects.
- You want a CC0-licensed list that can be reused or adapted with minimal copyright restrictions.
Look elsewhere if
- You need a recently maintained directory: the repository has had no commits in over a year and no releases in the past year.
- Your adoption decision depends on active project upkeep, since most contributions come from one person and there has been no recent issue or pull-request activity.
- You need a packaged tool or a verified recommendation rather than a list of external links.
All health signals
| Last commit | 2024-08-11 (2.2 years ago) |
|---|---|
| Commits, last 90 days | 0 |
| Releases, last 12 months | 0 |
| Contributors | 21 (top contributor: 76% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 0 |
| Project age | 12 years |
Checked on 2026-10-29 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
4,595Forks
350Change since Nov 11, 2026: 0 stars·0 forks
Overview
LewisJEllis/awesome-lua is a curated list for people working with Lua, the scripting language. It brings together packages and resources so developers can discover tools for areas such as game development, web services, testing, networking, and embedding Lua, alongside tutorials and references for learning the language.
This is a directory, not a software package or runtime: it points to external projects and resources rather than installing or providing them. Its broad scope makes it useful as an ecosystem map, though readers should check each linked project's current status and compatibility before adopting it.
Key Features
- Organizes Lua packages into categories including interpreters, package managers, debugging, game development, web platforms, testing, and data stores.
- Covers multiple ways to use Lua, including LuaJIT, OpenResty, LÖVE, and Lua bindings for other languages.
- Lists tools for common development tasks such as linting, profiling, documentation, serialization, and command-line parsing.
- Includes learning materials such as tutorials, books, articles, talks, and the official language reference.
- Links to Lua communities, style guides, and other focused resource lists.
- Accepts community contributions, with a contribution guide in the repository.
Use Cases
- A Lua developer choosing a library for a specific need, such as testing, JSON parsing, or database access, can use the relevant category to find candidates.
- A game developer exploring Lua frameworks can compare resources listed for platforms such as LÖVE and MOAI.
- A team evaluating Lua for scripting or web services can survey interpreters, bindings, and platforms such as OpenResty before selecting a stack.
- Someone learning Lua can use the tutorials, books, and reference links as a starting point, then verify that materials match their target Lua version.
Getting Started
Browse the categories in the README to find packages or learning resources. For contributing, start with the repository's contribution guidelines.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Considerations
The repository is marked inactive based on having no commits in over a year. Although it has contributions from multiple people, contribution activity is concentrated mostly in one person, and the measured data shows no recent issue closures or merged pull requests. The README is a collection of links, so inclusion should not be treated as confirmation that a dependency is maintained, secure, or compatible with a particular Lua version. The list itself is marked CC0 in the README, but that does not change the licenses or obligations of the external projects it links to.
Found this useful?
Share it with someone who would like awesome-lua.