Scan a public GitHub repository for stale feature flags
FlagShark clones the repository, runs the open-source @flagshark/core scanner over its source, and reports the flag references that look stale. One repository at a time. No sign-in.
What this report can and cannot tell you
- It is a static scan of the default branch at the date shown. The scanner reads source files and matches calls to the flag SDKs it recognises; it does not run the code.
- A reference counts as stale when its line was last changed more than 90 days ago according to git blame, or when every reference to that flag is in a test file. “Used in one file” is shown as context and never makes a flag stale on its own.
- Staleness comes from the code and its git history only. FlagShark did not query your flag provider, so it cannot see rollout state, evaluation counts or whether a flag is archived. An old line can belong to a flag that is still in use, such as a long-lived kill switch.
- Counts include test files and fixtures. Flags read through wrappers or keys the scanner does not recognise are not counted.
- The health score is computed by the scanner from these counts. It is not a benchmark against other repositories.
Private repositories
This page scans public repositories only. For a private repository, install the FlagShark GitHub App on the repositories you choose. The App opens cleanup pull requests, so it asks for read and write access to repository contents.
Install the GitHub App