FlagLint Is Now Listed on the OpenFeature Ecosystem
FlagLint is now listed in the OpenFeature ecosystem directory as one of two integrations in the JavaScript/Server category.
I want to be straightforward about what that means — and what it doesn’t.
What the listing is
Section titled “What the listing is”The OpenFeature ecosystem is a directory maintained by the OpenFeature project (a CNCF incubating standard) where providers, SDKs, hooks, and integrations can be listed. It is not an award or a certification. It is a discovery page. Teams that are already evaluating OpenFeature — researching providers, looking for tooling, trying to understand the ecosystem — land there.
Being listed means that those teams will now find FlagLint when they filter for integrations. That matters because the people who need FlagLint most are exactly the people who are actively thinking about OpenFeature.
Why I submitted
Section titled “Why I submitted”The OpenFeature standard is the reason FlagLint exists. The whole problem FlagLint solves — the argument-order inversion between LaunchDarkly’s boolVariation(key, ctx, default) and OpenFeature’s getBooleanValue(key, default, ctx) — only surfaces when you are trying to move to OpenFeature. If teams weren’t adopting OpenFeature, there would be no migration to get wrong.
So it made sense to be in the directory where those teams are looking. Not to market FlagLint as a product, but to be findable at the point in the journey where someone is asking “what tooling exists around OpenFeature for LaunchDarkly migration?”
What FlagLint does in the context of OpenFeature
Section titled “What FlagLint does in the context of OpenFeature”FlagLint is not an OpenFeature SDK or provider. It doesn’t evaluate flags. What it does is sit at the boundary between your existing LaunchDarkly codebase and the OpenFeature world you’re moving toward.
Specifically:
- Audit — inventory every direct LaunchDarkly SDK call, classify each one by migration risk, produce a readiness score
- Migrate — preview and apply proven-safe call-site rewrites that transpose arguments correctly and rename methods atomically
- Validate — enforce in CI that no new direct LaunchDarkly calls land once you’ve drawn the boundary
None of that requires a network connection, an API key, or access to your LaunchDarkly environment. It’s all static analysis on your source code, running locally.
Where to start
Section titled “Where to start”If you’re in the process of moving to OpenFeature and want to understand your current exposure before touching any code, the audit command is the right starting point.
npx flaglint@latest audit ./srcIt runs in under a minute on most codebases and doesn’t touch any files.