Weekly OSS Outreach Run — 2026-07-07
Search query: launchdarkly-node-server-sdk language:TypeScript (sorted by stars)
Cutoff: pushed within 6 months (after 2026-01-07), not a fork, not in launchdarkly or flaglint orgs
Qualifying threshold: 3+ flags found AND readiness score < 80
Result: 0 repos qualified this week
No outreach drafts to review. All repos that passed the date/fork/org filters were audited and failed the 3+ flag threshold.
Repos Audited
| Repo |
Stars |
Last Push |
Flags Found |
Readiness |
Outcome |
novuhq/novu |
39,263 |
2026-07-07 |
1 (* bulk via React hooks) |
0/100 |
< 3 flags |
open-feature/playground |
76 |
2026-06-30 |
0 (abstracted via OpenFeature) |
— |
< 3 flags |
rebeccarich/nuxt-launch-darkly |
4 |
2026-06-30 |
0 (module wrapper) |
— |
< 3 flags |
atlassian-labs/figma-for-jira |
4 |
2026-05-12 |
1 (dynamic key via wrapper) |
0/100 |
< 3 flags |
hardik-bhalekar/Syncora |
0 |
2026-05-18 |
0 |
— |
< 3 flags |
shakecodeslikecray/whiterose |
12 |
2026-02-13 |
0 (LD used for detection only) |
— |
< 3 flags |
ld-glynn/ld-metric-simulator |
0 |
2026-02-03 |
1 (dynamic key via wrapper) |
0/100 |
< 3 flags |
X-oss-byte/Novu |
0 |
2026-06-20 |
1 (React hook, old snapshot) |
0/100 |
< 3 flags |
ld-glynn/ld-metric-simulator |
0 |
2026-02-03 |
1 (dynamic key via wrapper) |
0/100 |
< 3 flags |
Why Nothing Qualified
The pattern across 162 code search results and 10+ pages of scanning was consistent: OSS TypeScript repos using launchdarkly-node-server-sdk overwhelmingly wrap the SDK behind a single service class (e.g. FeatureFlagsService, getLdFlag()) or use React's useFlags()/useLDClient() bulk hooks. FlagLint's static analysis can see the wrapper's single dynamic call point but not the individual string-literal flag keys scattered through business logic.
Many repos had rich LD flag usage but were outside the 6-month window:
formfunction-hq/formfunction-monorepo (72★, pushed 2023-04-10) — LaunchDarklyFlag enum + multiple callsitesnear-daos/astro-ui (37★, pushed 2023-01-18) — multiple direct variation callsnear-daos/astro-api-gateway (15★, pushed 2023-01-17) — full FeatureFlagsService with named flags
Recommendation
Consider broadening the search to include the newer @launchdarkly/node-server-sdk package name (LaunchDarkly's rebranded package), or relaxing the 6-month recency window to 12 months to capture the formfunction-monorepo-class repos that have genuine multi-flag usage.
Run by the automated OSS outreach agent — no external issues were posted.
Weekly OSS Outreach Run — 2026-07-07
Search query:
launchdarkly-node-server-sdk language:TypeScript(sorted by stars)Cutoff: pushed within 6 months (after 2026-01-07), not a fork, not in
launchdarklyorflaglintorgsQualifying threshold: 3+ flags found AND readiness score < 80
Result: 0 repos qualified this week
No outreach drafts to review. All repos that passed the date/fork/org filters were audited and failed the 3+ flag threshold.
Repos Audited
novuhq/novu*bulk via React hooks)open-feature/playgroundrebeccarich/nuxt-launch-darklyatlassian-labs/figma-for-jirahardik-bhalekar/Syncorashakecodeslikecray/whiteroseld-glynn/ld-metric-simulatorX-oss-byte/Novuld-glynn/ld-metric-simulatorWhy Nothing Qualified
The pattern across 162 code search results and 10+ pages of scanning was consistent: OSS TypeScript repos using
launchdarkly-node-server-sdkoverwhelmingly wrap the SDK behind a single service class (e.g.FeatureFlagsService,getLdFlag()) or use React'suseFlags()/useLDClient()bulk hooks. FlagLint's static analysis can see the wrapper's single dynamic call point but not the individual string-literal flag keys scattered through business logic.Many repos had rich LD flag usage but were outside the 6-month window:
formfunction-hq/formfunction-monorepo(72★, pushed 2023-04-10) —LaunchDarklyFlagenum + multiple callsitesnear-daos/astro-ui(37★, pushed 2023-01-18) — multiple direct variation callsnear-daos/astro-api-gateway(15★, pushed 2023-01-17) — full FeatureFlagsService with named flagsRecommendation
Consider broadening the search to include the newer
@launchdarkly/node-server-sdkpackage name (LaunchDarkly's rebranded package), or relaxing the 6-month recency window to 12 months to capture theformfunction-monorepo-class repos that have genuine multi-flag usage.Run by the automated OSS outreach agent — no external issues were posted.