Project
Reverse Dependencies for openfeature-sdk
The projects listed here declare openfeature-sdk as a runtime or development dependency
0.01
The flagd provider for the OpenFeature Ruby SDK
2021
2022
2023
2024
2025
2026
0.01
Flagsmith provider for the OpenFeature Ruby SDK
2021
2022
2023
2024
2025
2026
0.01
OpenFeature Flipt Provider for Ruby
2021
2022
2023
2024
2025
2026
0.01
The GO Feature Flag provider for the OpenFeature Ruby SDK
2021
2022
2023
2024
2025
2026
0.01
The MetaProvider wraps multiple other providers and uses a given strategy to resolve flags using all of them.
2021
2022
2023
2024
2025
2026
0.0
Confidence provider for the OpenFeature SDK
2021
2022
2023
2024
2025
2026
0.0
OpenFeature Provider that allows ConfigCat to be used with the OpenFeature Ruby SDK.
2021
2022
2023
2024
2025
2026
0.0
DevCycle Ruby Server SDK, for interacting with feature flags created with the DevCycle platform.
2021
2022
2023
2024
2025
2026
0.0
Kameleoon OpenFeature provider for the Ruby SDK
2021
2022
2023
2024
2025
2026
0.0
A LaunchDarkly provider for use with the OpenFeature SDK
2021
2022
2023
2024
2025
2026
0.0
The rollout provider for the OpenFeature Ruby SDK
2021
2022
2023
2024
2025
2026
0.0
Providers and Hooks for the OpenFeature Ruby SDK
2021
2022
2023
2024
2025
2026
0.0
A Ruby provider for OpenFeature that integrates with Subflag's feature flag management system. Supports boolean, string, number, and object flag types with evaluation context.
2021
2022
2023
2024
2025
2026
0.0
Feature flags for Rails with selectable backends. Use Subflag Cloud (SaaS), ActiveRecord (self-hosted), or Memory (testing). Get typed values (boolean, string, integer, double, object) with the same API regardless of backend.
2021
2022
2023
2024
2025
2026