Open-source project
sainnhe/everforest avatar
sainnhe/everforest

Everforest ships six variants and keeps its docs in a help file

🌲 Comfortable & Pleasant Color Scheme for Vim

4,282 stars143 forksVim ScriptMIT

At a glance

What is it?
Everforest is a warm green colour scheme for Vim with a short feature list and an even shorter readme: six variants, a palette document, and documentation that lives in a Vim help file rather than on the page. What the page does not contain is an install command.
Who is it for?
Everforest fits someone who wants a warm green colour scheme for Vim, since the variant naming lets you pick contrast independently of background. It does not fit someone who wants a documented install flow, because the page documents none and defers to a help file, and it does not fit a repository that releases colour schemes as tagged versions, since there are no releases at all and the tree is the distribution.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 160 days ago.
What is it written in?
Mainly Vim Script, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • sainnhe/everforest4,282 ★ · +53
Star history
Repository2026-09-232026-11-15
sainnhe/everforest4.2k4.3k

53 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Six variants from two axes, not three names

The page shows the variant table before it says anything else, and the table is more informative than the introduction. Three rows carry the contrast levels: Hard, Medium and Soft. Two columns carry the backgrounds: Dark and Light. That is six variants, and the important detail is that the two axes are independent.

Most schemes name a variant after both of its properties at once, which means choosing a light background also fixes the contrast you get. Here you can ask for a soft light scheme or a hard light scheme, and the name tells you which of the two you are changing.

The philosophy behind the numbers is one sentence: green based, designed to be warm and soft in order to protect developers' eyes. The README says it is designed to have soft contrast for eye protection.

The feature list is a compatibility list, and italics need a font

For a colour scheme, the feature list is really a statement about which highlighting systems it feeds. This one names tree-sitter support, semantic highlighting support, and rich support for common file types and plugins.

Those three lines cover the two ways Vim and its successors decide colour. Tree-sitter parses the file into a syntax tree and asks the theme for colours per node, while semantic highlighting asks for colours per meaning, so a theme that supports both has to define colours for two different vocabularies.

Then there is italic support, linked to a page about fonts, which is the one feature that cannot live in a colour file alone. Italic text needs a font with italic glyphs, so the page points you at typography rather than at a palette value.

Everything else on the list is one line: warm-toned green, soft contrast, and customizable.

Redshift and f.lux are named as companions

Two external tools are named directly in the features: redshift, a screen colour temperature adjuster for the command line, and f.lux, its desktop equivalent. Both are listed under the claim that the scheme works well with them.

That pairing explains an otherwise odd design decision. A scheme described as warm-toned is not trying to be colour-accurate, and a palette that already sits in the warm end of the spectrum is the one that survives being pushed further by a system-level filter.

The other named tools in the project are of a different kind. The documentation is a Vim help file rather than a site, the palette and highlighting semantics live in a markdown document at the repository root, and related projects are collected on a wiki page instead of a list in the readme.

So the page's own idea of documentation is: install from the tree, read help inside the editor, read the palette document when you want the numbers.

The tree is a Vim plugin layout, and there is no install command

The repository root is small and follows Vim's own conventions. There is a colors directory, which is where a colour scheme has to live for Vim to find it, an autoload directory for lazily loaded functions, a doc directory holding the help file, and a lua directory for Neovim users.

Alongside those are the readme, the licence, a palette document, and two directories that say something about how the project is worked on: a hooks directory for Git and a directory for GitHub configuration.

What is missing is the thing most visitors look for. There is no installation command anywhere on the page, no line to copy into a configuration manager, and no release to download. The documentation link goes straight to the help file, which in Vim is reached by asking for help on the topic name.

That is a defensible choice for a colour scheme, since the install is a file copy into a directory Vim already searches.

Customizable is the one feature with no link next to it

The feature list is a set of single lines, and only one of them is a bare adjective: customizable. Everything else either names a system or carries a link.

The place to go for the actual colours is the palette document, linked under the palette heading as the colour palette and highlighting semantics. It is the only artefact in the repository that would let someone adjust the scheme without reading the colour files.

That distinction matters because the two jobs are different. Adjusting a palette means choosing new values for a documented set of roles, while reading the colour files means learning which file defines which highlight group and how the groups map to each highlighting system.

For the second job the help file is the reference, and it lives in the repository rather than on a site, which is why the documentation link on the page points into the tree.

Three maintainers, three sibling schemes, four inspirations

The credit section is a table of three people: Sainnhe Park, Jef LeCompte and Antoine Cotten. The licence is MIT, attributed to the first of them.

The same author publishes three other schemes alongside this one, named Gruvbox Material, Edge and Sonokai, which is worth knowing before installing them all into the same editor.

Then there is the inspirations list, four repositories: a spring night colour scheme, a sacred forest scheme, gruvbox, and a solarized scheme. Gruvbox appears twice in this project, once as an inspiration and once as the name of a sibling scheme, so the lineage is easy to trace.

Related projects are not listed in the readme at all. That section points at a wiki page instead.

Git hooks are committed and there are no releases

Two structural details say how this project ships. The first is the absence of releases: the repository has no GitHub releases at all, and no tags are referenced anywhere on the page.

For a colour scheme that is coherent. A scheme is a directory of files that an editor reads at startup, so there is nothing to publish as an artefact and no binary compatibility question to answer. Updating means copying files again.

The second detail is the hooks directory in the tree. Commit hooks are usually a local setting under the Git directory and are not shared, so keeping them in the repository means they can be installed deliberately and versioned with the scheme.

Together they describe a project distributed by copying, which is also why the last push on the default branch, dated 2026-06-08, is the only signal of activity available to a visitor.

Editorial conclusion

Everforest fits someone who wants a warm green colour scheme for Vim, since the variant naming lets you pick contrast independently of background. It does not fit someone who wants a documented install flow, because the page documents none and defers to a help file, and it does not fit a repository that releases colour schemes as tagged versions, since there are no releases at all and the tree is the distribution. Before adopting it, check four things. Which of the six variants you want, because the naming crosses three contrast levels with two backgrounds and picking by name alone is guesswork. Which highlighting systems you need covered, since tree-sitter, semantic highlighting and italics are listed as features and each depends on your editor and font. Whether you want the palette as shipped or adjusted, since the one feature called customizable has no link beside it while the palette document does carry the semantics. And which of the author's other schemes it might duplicate, because Gruvbox Material, Edge and Sonokai come from the same hands and gruvbox is also credited as an inspiration.

Frequently asked questions

How do I install the Everforest theme?

The page carries no install command. Its documentation is a Vim help file reached with :help everforest.txt, and the repository holds the colour files under colors/, autoload code, Lua files for Neovim and the help file under doc/. For the colours themselves there is a palette document at the repository root.

Which variants does Everforest have?

Six, from two independent axes: three contrast levels named Hard, Medium and Soft, each offered against a dark and a light background. That means a light scheme is not fixed to one contrast level.

Does Everforest support tree-sitter and semantic highlighting?

Both are listed among its features, along with support for common file types and plugins. Italic support is listed too, with a link to a page of fonts, since italics need a font rather than a palette value.

Who maintains Everforest and what licence is it under?

Three maintainers are listed: Sainnhe Park, Jef LeCompte and Antoine Cotten. The licence is MIT. The same author also publishes Gruvbox Material, Edge and Sonokai as other colour schemes.

Does Everforest work with redshift or f.lux?

Both are named in the features as tools the scheme works well with, which fits a palette that is deliberately warm-toned rather than colour-accurate.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. sainnhe/everforest on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sainnhe-everforest.svg)](https://hysenlabs.com/projects/sainnhe-everforest)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sainnhe-everforest.svg)](https://hysenlabs.com/projects/sainnhe-everforest)

Was this useful?