Why Open Apps?
- Real applications, not toy projects — complete products with meaningful
scope, structure, and a clear license.
- Practical discovery — browse by category, platform, stack, activity, and
maturity.
- Useful learning signals — understand what a project is best for, how
difficult it is, and what architectural ideas it demonstrates.
- Fresh repository metadata — scheduled automation refreshes activity and
contributor data through reviewable pull requests.
- Open, portable data — every catalog entry is a human-readable YAML file
in this repository.
What belongs in the directory?
- tutorials, snippets, or one-screen demos;
- boilerplates and starter templates;
- package-only libraries and SDKs;
- archived projects with no enduring learning value;
- repositories with an unclear license or purpose.
Local development / Requirements
- pnpm 10.12.1 (the version is pinned in
package.json)
Add or update an app / Useful commands
- Create or edit
data/apps/<slug>.yml.
- Keep human-owned fields under
app, stack, and curation.
- Do not hand-edit automation-owned
github or health fields.
- Run
pnpm validate:data, pnpm test, and pnpm build.
- Open a focused pull request.
Automation / Useful commands
- pull requests that touch catalog data run schema validation, data generation,
and unit tests;
- app activity and GitHub-shaped metadata are refreshed daily;
- repository contributor statistics are refreshed weekly;
- stale-app candidates are reported weekly for curator review.
AI-readable catalog / Useful commands
llms-full.txt — the expanded
catalog for AI assistants and retrieval tools.
]]>