Skip to content
You must be logged in to sponsor shirou

Become a sponsor to shirou

@shirou

shirou

Tokyo

I am an main author of and also several kind of Open Source projects.

I am the creator of gopsutil, a popular and widely-used library with over 10k stars on GitHub. gopsutil provides a simple and reliable way to access system and process information across different platforms. gopsutil is used by more than 30k repositories and it’s trusted by many well-known projects, including Kubernetes, OpenTelemetry, Nomad, making it a cornerstone in performance monitoring, data collection, and system analysis tools.

Maintaining gopsutil requires a significant investment of time and resources. By becoming a sponsor, you directly support ongoing development, bug fixes, new feature additions, and timely updates. Your contribution helps keep the project alive and thriving, benefiting the entire open-source community.

Why Sponsor?

  • Sustain Development: Help keep gopsutil up-to-date and compatible with the latest systems.
  • Accelerate Features: Enable quicker development of new features that benefit the entire community.
  • Show Appreciation: Your support encourages continued maintenance and improvements.

Every contribution, big or small, makes a difference. Thank you for considering sponsoring gopsutil and supporting the open-source ecosystem!

Featured sponsors

@fwessels
Private Sponsor
@erwanor
@jahkeup
@baryluk
@TylerCode
@Notifiarr
Past sponsors 8
@Notifiarr
@baryluk
@jahkeup
@TylerCode
@erwanor
Private Sponsor
@fwessels
@github

Featured work

  1. shirou/gopsutil

    psutil for golang

Select a tier

$ a month

Choose a custom amount.

$5 a month

Select

Buy me a Beer 🍺 or Japanese-Sake 🍶 every month. You will receive a Sponsor badge on your profile!

$10 a month

Select

Support the cost of the Cloud Instances we are creating for development.

$200 a month

Select

Gold Sponsor: Support for my new machines which I can not develop due to lack of real machine, such as Mac M2 or s390x.I will add your name at the end of the README.