# Status of BenchmarkCI

**URL:** <https://discourse.julialang.org/t/status-of-benchmarkci/121530>\
**Category:** General Usage\
**Created:** [October 21, 2024, 12:30pm UTC](https://discourse.julialang.org/t/status-of-benchmarkci/121530 "2024-10-21T12:30:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![SamBrand](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@SamBrand](https://discourse.julialang.org/u/SamBrand)\
**Post date:** [October 21, 2024, 12:30pm UTC](https://discourse.julialang.org/t/status-of-benchmarkci/121530/1 "2024-10-21T12:30:27Z")

</div>

Hi everyone,

I’m using [BenchmarkCI.jl](https://juliahub.com/ui/Packages/General/BenchmarkCI) as part of my suite of CI in a project.

I’ve noticed that its been unmaintained for a while, and now I have a problem with `[compat]` (BenchmarkCI can’t be used with `DiffEqBase.jl` due to `Setfield.jl` incompatibility). I believe that the maintainer @tfk has stopped supporting his projects (no judgment, just an observation!)

Is there a common protocol in the Julia community for dealing with infrastructure packages that get unmaintained?

My short term fix is going to be fork the repo and then point at my fork with `[sources]`, but that seems non-ideal.

---

<div class="post-metadata">

**Author:** ![vchuravy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vchuravy/32/8_2.png) [@vchuravy](https://discourse.julialang.org/u/vchuravy)\
**Post date:** [October 21, 2024, 4:21pm UTC](https://discourse.julialang.org/t/status-of-benchmarkci/121530/2 "2024-10-21T16:21:19Z")

</div>

TKF has sadly not been seen around these parts for a while,  
so yes the answer is to fork it to an Org like JuliaCI or JuliaPerf where multiple people can maintain the package or switch to something like [GitHub - MilesCranmer/AirspeedVelocity.jl: Easily benchmark a Julia package over its commit history](https://github.com/MilesCranmer/AirspeedVelocity.jl)