Open-source project
Tyrrrz/LightBulb avatar
Tyrrrz/LightBulb

LightBulb shifts screen gamma by time of day, and its README attaches four political conditions to using it

Reduces eye strain by adjusting screen gamma based on the current time

2,827 stars177 forksC#MIT

At a glance

What is it?
LightBulb is a C# Windows application that continuously adjusts display gamma from cold blue to warm yellow as the day turns, with sunrise and sunset times taken from your location or set by hand. Two things on the page deserve attention before you install it: the download section routes three of four options through community package managers that the page warns can lag, and the README states that using the project for any purpose means implicitly agreeing to four statements about the war in Ukraine.
Who is it for?
LightBulb does one small thing with the display driver and does it continuously, so it suits anyone who has ever ended a late session with sore eyes and wants the fix to be automatic rather than a settings change. Three things to check first.
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 9 days ago.
What is it written in?
Mainly C#, 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

  • Tyrrrz/LightBulb2,827 ★ · +27
Star history
Repository2026-10-042026-11-15
Tyrrrz/LightBulb2.8k2.8k

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

Editorial analysis

The license file is MIT, and the README adds four conditions on use

The repository carries an MIT license in a file named License.txt, which is the grant most people will read and the one that governs the code as published. Separately, the README has a terms of use section that says using the project or its source code, for any purpose and in any shape or form, grants implicit agreement to four statements. They concern Russia's military aggression against Ukraine, treating Russia as an occupant that unlawfully invaded a sovereign state, support for Ukraine's territorial integrity including its claims over temporarily occupied territory in Crimea and Donbas, and rejection of narratives attributed to Russian state propaganda. The section links to a page about the war and invites support. Neither the README nor the license file explains how the two relate, and this project is not the only one where a license text and a README clause sit side by side. What a reader can say with certainty is that both exist, that one is a license grant and the other is a statement about use, and that whether the second constrains anything is a question for whoever relies on it.

Four download routes, three of them maintained by other people

The download section offers four ways in, and only one is built by the project itself. There is a stable release link and a continuous integration build link for people who want the newest commit rather than the newest release. Then there are three package managers, each labelled community-maintained in the same parenthetical:

bash
winget install Tyrrrz.LightBulb
bash
scoop install extras/lightbulb
bash
choco install lightbulb

A note under the list says those packages are published independently from this repository and may not always be up to date with the latest release, which is the sentence to keep in mind when a package manager reports a version behind the GitHub one. A second note points at a user agent lookup page for working out your operating system and CPU architecture, which is a small signal that the builds are architecture specific. Nothing on the page lists a Linux or macOS package, so the four routes are all ways to get a Windows build.

The mechanism is gamma, adjusted continuously rather than in steps

What the application does is narrow and worth stating precisely. It continuously adjusts gamma, which moves the display colour temperature from a cold blue in the afternoon toward a warm yellow during the night. The stated objective is to match the screen to the light sources of the surrounding environment, sunlight during the day and artificial light at night, rather than simply dimming or brightening it. The transitions are described as smooth, so the change is not something you notice happening, and the performance cost is described as minimal. Because gamma is a colour operation rather than a brightness one, the practical consequence is that anything you judge colour with will also be shifted, which is why the feature list includes a whitelist for colour sensitive applications. Global hotkeys exist for adjusting on the fly, which is the escape hatch when the automatic schedule is not what you want at 4pm.

Sunrise and sunset come from your location or from numbers you type

The schedule that drives the transition has two sources. Location based sunrise and sunset times mean the application derives the curve from where you are, and the feature list also states that the application works without an internet connection, which implies the calculation is done locally rather than fetched. Manual sunrise and sunset times are the second source, for anyone behind a schedule the location cannot know about, for shift work, or for anyone who simply wants a fixed warm tint at a chosen hour. Which one is active is part of the configuration rather than something the page spells out, since it points at the wiki for questions and issues. The two sources being listed side by side, rather than one being described as a fallback for the other, is the design choice that makes this usable outside a normal day.

Four projects, one XML solution file, and a pinned SDK

The repository layout shows a current .NET shape. There is a solution file named LightBulb.slnx, which is the XML form rather than the older text format, and beside it Directory.Build.props for shared build properties and Directory.Packages.props, which is how central package version management is configured, plus a NuGet.config and a global.json that pins the SDK the build expects. The code is split into LightBulb.Core for the logic, LightBulb.PlatformInterop for the calls into the platform, LightBulb for the application itself, and LightBulb.Core.Tests for tests. That split is the interesting part: gamma adjustment is a platform call, and keeping it behind an interop project is what leaves something testable on the other side. An Installer directory sits alongside them, and the root also carries an assets directory, two favicon files in ico and png, and a readme whose file name is capitalised as ReadMe.md.

Support goes to a wiki, and the badge row points at status and coverage

The page routes support away from itself. If you have questions or issues, it says, refer to the wiki, and the documentation for anything beyond the summary lives there. The badge row gives the rest of the shape: a link to a project status document in the author's shared profile repository, a link to a personal page, the actions page, a code coverage service badge wired to this repository, the releases page twice, a Discord invite and a Twitter status link. There is also a banner stating that development of the project is entirely funded by the community, with a donation link. Read together with the layout, that is the profile of a single maintainer with a test project, coverage reporting and a community donation model, which is worth knowing before you file an issue expecting a response window.

The README stops at a Screenshots heading, and the homepage is the releases page

Two small facts about how this page is arranged. The last heading on it is Screenshots, with nothing under it, so the visual examples the project would normally lead with are not present in the text. And the homepage recorded for the repository is the releases page rather than a documentation site, which means there is no site to fall back on: the wiki and the releases are the whole public surface. Version history shows 2.7 on 10 March 2026, 2.7.1 on 19 May 2026 and 2.7.2 on 10 September 2026, and the last commit on the default branch is dated the same day as 2.7.2, so the tag and the tip of the branch were in step at that point. The default branch is named prime rather than main, which is the author's convention across projects and not a sign of anything specific to this one.

Editorial conclusion

LightBulb does one small thing with the display driver and does it continuously, so it suits anyone who has ever ended a late session with sore eyes and wants the fix to be automatic rather than a settings change. Three things to check first. Read the terms of use section as well as the license file, because the two say different things about what using the code agrees you to, and that is a decision for you rather than for a reviewer. Prefer the stable release or a pinned package version over the floating package manager entries, since the page itself warns that community packages may lag. And if you do colour work, add the affected applications to the whitelist before you start, because gamma shifting will otherwise distort anything you judge colour with.

Frequently asked questions

How does LightBulb change the colour of the screen?

It continuously adjusts gamma, moving the display colour temperature from cold blue in the afternoon to warm yellow during the night, with the stated aim of matching the surrounding light sources, sunlight by day and artificial light at night. Transitions are described as smooth and the performance impact as minimal.

How do I install LightBulb on Windows?

Four routes: the stable release, a continuous integration build, or one of three package managers, winget install Tyrrrz.LightBulb, scoop install extras/lightbulb and choco install lightbulb. The three package manager entries are labelled community-maintained, and a note warns they may not be up to date with the latest release.

Does LightBulb need an internet connection?

It is listed as working without one. Sunrise and sunset times can be derived from your location or entered manually, and the colour adjustment itself is local to the machine.

What are the terms of use attached to LightBulb?

The README states that using the project or its source code, for any purpose and in any shape or form, grants implicit agreement to four statements about Russia's invasion of Ukraine, Ukraine's territorial integrity, and narratives attributed to Russian state propaganda. The repository separately carries an MIT license in License.txt, and the two are not reconciled on the page.

Which platforms does LightBulb build for?

The download section lists a stable release, a CI build and three Windows package managers, with a note pointing at a user agent lookup page for operating system and CPU architecture. No Linux or macOS package is listed, and the solution is split into LightBulb.Core, LightBulb.PlatformInterop, LightBulb, LightBulb.Core.Tests and an Installer project.

Where do I get help with LightBulb?

The page sends questions and issues to the project wiki, and says nothing further about response times. Development is described as entirely funded by the community with a donation link, and the badges point at a project status document, the actions page and a coverage report.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. Tyrrrz/LightBulb 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/tyrrrz-lightbulb.svg)](https://hysenlabs.com/projects/tyrrrz-lightbulb)

Star history chart for your README

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

Was this useful?