Skip to content

Unleash client SDK for Java

active 2025-08-012026-07-15 (UTC)

Complete coverage26,370 / 26,370 hourly files (100%) · 2 absent upstream2023-08-152026-08-17 (UTC)
Events
411
Pushes
110
Pull requests
29
Issues
15
Stars
4
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 349 days from 2025-08-01 to 2026-07-15. Pushes: 110 total, peak 9 in a day. Pull requests: 29 total, peak 3 in a day. Issues: 15 total, peak 4 in a day. Comments: 119 total, peak 13 in a day. Stars: 4 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#378coveralls2026-05-22 08:40
    task: Use getInputStream to get data
  • Issue comment#375gastonfournier2026-04-17 11:47
    launchdarkly eventsource-okhttp dependency needs an upgrade due to okio CVE
  • Issue#346chriswk2026-03-19 08:33
    Missing /native/libyggdrasilffi_x86_64.dylib on Intel Mac
  • Issue comment#369melindafekete2026-02-20 10:26
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Releaseunleash-bot[bot]2026-02-19 09:45
    Release v12.1.2
  • Issue#369chriswk2026-02-19 09:17
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Issue comment#370coveralls2026-02-19 08:49
    fix: strategy evaluation is OR based.
  • Issue comment#369kanishka-shashan2026-02-18 09:49
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Issue comment#369chriswk2026-02-18 09:45
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Issue#369gastonfournier2026-02-18 08:42
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Issue#369gastonfournier2026-02-18 08:42
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Issue#369kanishka-shashan2026-02-18 08:38
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Issue#369gastonfournier2026-02-18 08:38
    Adding the same custom strategy multiple times on a feature flag does not evaluate all instances (last one wins)
  • Pull request#368gastonfournier2026-02-09 09:30
  • Issue#367marcindabrowski2026-02-05 14:15
    Lack of replacement for strategies removed in version 10
  • Issue comment#365coveralls2026-01-28 12:23
    fix: handle infinity,nan + deprecation notice
  • Issue comment#364coveralls2026-01-26 21:59
    chore(deps-dev): bump org.assertj:assertj-core from 3.27.6 to 3.27.7
  • Issue comment#363coveralls2026-01-22 18:30
    chore(deps-dev): bump ch.qos.logback:logback-core from 1.5.20 to 1.5.25
  • Pull request#362chriswk2026-01-22 15:31
  • Pull request#362chriswk2026-01-22 15:31
  • Pull request#361sjaanus2026-01-22 10:28
  • Issue comment#361mergify[bot]2026-01-22 05:46
    fix: change gauge from long to double
  • Pull request#359kwasniew2026-01-21 10:30
  • Issue#357sighphyre2026-01-15 08:24
    Version 12: `java.lang.NoClassDefFoundError` thrown by `new DefaultUnleash(unleashConfig)`
  • Pull request#358sighphyre2026-01-15 08:24

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 4 stars here means stars gained during the window, not the repo's star count.