Project Health

  • 2 active maintainers
  • PRs continuously submitted and merged
  • 2 Mentorship projects successfully finished
  • Questions on Discord and GitHub are regularly answered
  • Monthly contributor calls (discussion happens mostly on Discord, as needed)

Required Information

  1. Have you switched from master to main in all your repos? → Yes
  2. Have you implemented the Common Repository Structure in all your repos? → Yes 
  3. Has your project implemented these inclusive language changes listed below to your repo? You can optionally use the DCI Lint tool to make this a recurring action on your repo. → Yes
    1. master → main
    2. slave → replicas
    3. blacklist → denylist
    4. whitelist → allowlist
  4. Have you added an Inclusive Language Statement to your project's documentation and/or Wiki pages? → Yes (

Questions/Issues for the TSC

Not at this time.


The latest stable release is v0.5.0; we're also continuously publishing unstable releases after every merged PR:

Overall Activity in the Past Quarter

List of merged PRs (11):

Summary of activities:

  • CI pipeline improvements and fixes (as part of a mentorship project)
  • Added base skeleton for VSCode extension (as part of a mentorship project)
  • Improving Prometheus integration

Current Plans

  • Overview and decrease the issue backlog.
  • Create developer docs that exhaustively document internal Caliper workings. This will be the basis for proposing epic refactorings and improvements. And hopefully will help attract more core devs by lowering the entry barrier for project contributions.

Maintainer Diversity

Current maintainers.

Contributor Diversity

Contributions from maintainers and recent project mentees, Eravatee Raje and Rinish Sam.

Additional Information


Reviewed By

Submission date

$action.dateFormatter.formatGivenString("dd-MMM-yyyy", $content.getCreationDate())


  1. Attila Klenik – I think the plan to create developer docs to lower the barrier to entry for project contribution is a great idea.  Once that documentation is ready, I'd recommend that we schedule a workshop to walk people through that and get people up and running.  Workshops get hundreds of people signing up for them and this will help introduce Caliper to many new people.  If you'd like to talk up scheduling and promoting that, let me know.

    And I've had conversations recently with other people doing blockchain performance related work and I think there's an opportunity here to combine efforts and collaborate.  In particular, people involved with the Performance and Scale WG are working on the Performance Sandbox lab and I also spoke to a PhD candidate who is working on a blockchain benchmarking framework called Diablo.  If there's interest in collaborating with them, I'm happy to make introductions.

    1. Yes, I plan on joining the PSWG call next week to see what they are up to (I was absent lately since I just finished my PhD, also in the DLT performance topic (smile)). It would be nice to avoid effort duplication among tools and cooperate as much as possible. 

      1. Attila Klenik – Great, I'm glad to hear you're interested in exploring cooperating with the PSWG.  I'll connect you to Haris and Sam from the group over email since I'm not 100% of their plans for future calls.  I've been talking to them about the structure of the group and looking at maybe changing things to allow them to collaborate more with other projects.  We haven't decided what's best yet and getting your input would be helpful.