Introduction
Understand scanning, OpenFeature adoption, and reviewable flag cleanup in FlagShark.
FlagShark helps teams move application code toward OpenFeature and keep obsolete feature flags from accumulating. Start with the path that matches your task.
Choose a starting point
| Your goal | Start here | What to expect |
|---|---|---|
| Find feature flags in a repository | Free scanner quickstart | Open-source Action or CLI; no hosted account required |
| Replace vendor-specific application calls | OpenFeature adoption | Scoped migration assessment and pilot access; exact stack and call shapes determine available stages |
| Remove eligible obsolete flag code | Cleanup PRs | Hosted, policy-controlled draft PRs for supported patterns; human review and merge |
| Describe a private SDK or wrapper | Custom flag libraries | Detection configuration and a bounded semantic-profile path; no automatic promise of migration or removal |
OpenFeature adoption
The first migration focus is LaunchDarkly server-side Node.js/TypeScript. Application calls move to the OpenFeature API while LaunchDarkly continues to provide runtime evaluations and flag configuration through its OpenFeature provider. This reduces application coupling to the vendor API; it does not transfer targeting rules, move the control plane, or terminate your LaunchDarkly service.
Migration is scoped by the exact SDK, runtime and source pattern. Assessment, preview, draft PR and post-merge verification are distinct capabilities. Check the homepage support selector and request an assessment before planning a repository rollout. The deployed pilot admission and repository assessment determine what you can actually run.
Ongoing cleanup
Cleanup uses source evidence, provider evidence and your workspace policies to propose removal of eligible flags. A stale flag is a candidate for investigation, not proof that a branch is safe to delete. Generated changes remain reviewable PRs; FlagShark does not automatically merge them or silently delete provider flag definitions.
As of September 9, 2026, OpenFeature JavaScript/TypeScript cleanup is registered through draft PR, with narrower patterns than migration. Verified ongoing cleanup after migration is still being certified. See current cleanup boundaries before relying on the complete lifecycle.
Connect the hosted product
For hosted workflows, follow GitHub App installation, repository connection and LaunchDarkly integration. Migration pilot access is separate from scanner use and hosted cleanup plan access.
The language catalog describes detection. It does not mean every listed SDK/language combination supports migration, removal, verification or general availability.