Awesome EigenScript

A curated list of EigenScript packages, tools, examples, and learning resources.

This is a list, not a registry. EigenScript's package tool (eigenscript --pkg add) pins consumers to a git URL + tag — there is no install-time lookup against this index. Listing here is purely for discoverability.

Contents

• Packages
  • Getting Started
• Tools
• Learning
• Editor Integrations
• Showcase

Packages

Packages are git repos consumable via eigenscript --pkg add <owner>/<name> <git-url> [tag]. The tool requires the <owner>/<name> form — bare names are reserved. See the Contributing section for naming and versioning guidance.

Getting Started

• eigs-package-template — Forkable starting point for a new package. Layout, smoke test, CI workflow, and MIT license already wired up.

Tools

Build tools, formatters, linters, CI helpers — anything that wraps the eigenscript binary.

• eigenscript — The language itself. eigenscript --fmt, eigenscript --lint, and eigenscript --pkg are the built-in tools; make lsp builds the companion eigenlsp language server.
• homebrew-eigenscript — Homebrew tap. brew install InauguralSystems/eigenscript/eigenscript.

Learning

• docs/SPEC.md — Language reference. Examples are runnable.
• docs/STDLIB.md — Standard library reference.
• docs/COMPARISON.md — Side-by-side with Python and JavaScript.
• examples/ — Idiomatic examples in the language repo.
• Browser playground — Run EigenScript in the browser (WASM, interpreter-only).

Editor Integrations

• VS Code — TextMate grammar in the language repo.
• Vim — Syntax file in the language repo.
• LSP — make lsp builds the eigenlsp binary (installed alongside eigenscript by make install), which speaks the Language Server Protocol; point any LSP-capable editor at it.

Showcase

Real programs and projects written in EigenScript. (Empty for now — open a PR when you ship something.)

Contributing

PRs welcome. Two rules:

1. One package per PR. Add your entry under the right heading; if no heading fits, propose a new one in the PR description.
2. Format: **[name](url)** — one-line description. Keep descriptions to a single line; let the linked README do the selling.

Inclusion is at maintainer discretion: the package should solve a real problem, have a tagged release, and have at least a smoke test under CI. See CONTRIBUTING.md in the language repo for naming + versioning guidance.

License

The list itself is CC0 — public domain, do whatever. Individual linked projects keep their own licenses.