[opensourcedex]

Featurevisor is a free, open source application security project written in TypeScript and released under MIT. It has 808 GitHub stars, 38 forks and 7 open issues, and was last pushed 9 days ago. On this registry it ranks #12 of 16 tracked projects in Application Security, with 5 head-to-head comparisons available. It gained 1 stars over the last 6 tracked days.

What is Featurevisor?

What it is

Featurevisor is an MIT-licensed TypeScript project for feature management with GitOps. It lets developers manage feature flags, experiment variations, and remote configuration values declaratively inside a Git repository. The project lives in the GitOps feature management ecosystem, where Git is used to define product behavior and configuration.

The concrete problem it solves is the need to manage feature flags, experiments, and remote configuration values through version control instead of editing application code for each decision. Teams define features in a repository, build static JSON datafiles, serve those datafiles from a CDN or custom server, and evaluate them in the application through SDKs. This makes flag changes follow a Git workflow and gives teams a reproducible way to target users, run experiments, and expose typed configuration values.

Key capabilities

  • Manage feature flags, experiment variations, and remote configuration values declaratively in a Git repository.
  • Build static JSON datafiles that applications can fetch from a CDN or custom server.
  • Evaluate flags, variations, feature variables, and global variables against a context supplied by the application.
  • Define reusable targeting conditions through attributes and segments.
  • Support typed values through feature variables and independently evaluated global variables.
  • Provide SDKs for JavaScript, React, Vue.js, Next.js, Go, Python, PHP, Ruby, Java, Kotlin, Swift, Rust, Elixir, and OpenFeature providers.
  • Include an official skill for AI agents to create features and segments, write rollout rules and test specs, debug evaluations, promote between sets, and integrate SDKs.

Who uses it and how

  • Front-end teams add flags to React, Next.js, or Vue.js applications by fetching a datafile and evaluating it against user context.
  • Backend teams use JavaScript, Go, Python, PHP, Ruby, Java, Kotlin, Swift, Rust, or Elixir SDKs, or OpenFeature providers, to evaluate features in services and mobile clients.
  • Product teams run A/B tests by defining variations and targeting segments for experiment groups.
  • DevOps teams automate datafile builds and uploads through CI/CD pipelines such as GitHub Actions.

Getting started

Teams start by managing a Featurevisor project in a Git repository, building datafiles through CI/CD, and uploading them to a CDN or custom server, then applications fetch the datafile and use the relevant SDK to evaluate features. The official AI skill can be installed with npx skills add featurevisor/featurevisor.

When to use it — and when not to

Use Featurevisor when your team already works through Git and can supply a repository, CI/CD pipeline, and CDN or custom server for datafiles. It is less suitable when you do not want to operate those pieces yourself, because the README asks you to bring the Git, CI/CD, and serving infrastructure. The registry metadata lists 0 contributors, 7 open issues, and a 0-year repo age, so teams may need to verify community activity before adopting it.

project readme (upstream, from github) — read inline

Featurevisor

Feature management with version control

Manage your feature flags, experiment variations, variables for remote configuration
declaratively from the comfort of your Git workflow.

Website | Documentation | Issues | Contributing | Changelog

Built by @fahad19 and contributors

How does it work?

Three simple steps to visualize it:

Featurevisor

  1. Manage your Featurevisor project in a Git repository
  2. Build and upload datafiles (static JSON files) to your CDN or custom server
  3. Fetch the datafile in your application, and evaluate features using SDKs

What do I need to bring to use Featurevisor?

Featurevisor SDKs will take care of the rest for you.

Understanding the building blocks

The core building blocks of a Featurevisor project are:

  • Attributes: building block for conditions
  • Segments: reusable conditions for targeting users
  • Features: features with flag, variation, and variable definitions
  • Global variables: independently evaluated configuration values

SDKs evaluate feature values against the context provided by your application. All current Featurevisor SDKs support independent global variables:

Where can I use Featurevisor?

SDKs

Supported SDKs include:

Using Featurevisor with AI agents

Featurevisor ships an official skill that teaches AI agents (like Claude Code, Cursor, Codex, and OpenCode) how to work with your project: creating features and segments, writing rollout rules and test specs, debugging evaluations, promoting between sets, and integrating SDKs in your applications.

Install it in your Featurevisor project (or your app repository) via skills.sh:

$ npx skills add featurevisor/featurevisor

Then prompt your agent naturally:

  • "Create a showWishlist feature, tagged web, starting at 5% in production"
  • "Why is checkout disabled for userId 123 in the Netherlands?"
  • "Roll out newEditor to employees first, then beta users, then everyone"

Pair it with npx featurevisor catalog running locally to visually review every change your agent makes, live in the browser.

The skill's source lives in this repository under skills/.

Why should I use Featurevisor?

Several use cases include:

License

MIT © Fahad Heylaal

Frequently asked questions

Is Featurevisor free to use?

Featurevisor is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does Featurevisor do?

Feature management with GitOps for developers

What is Featurevisor written in?

Featurevisor is primarily written in TypeScript. Its source is publicly available at https://github.com/featurevisor/featurevisor, and it has 808 GitHub stars.