Skip to content
You must be logged in to sponsor shenxianpeng

Become a sponsor to Xianpeng Shen

@shenxianpeng

Xianpeng Shen

shenxianpeng
Lithuania

Hi, I'm Xianpeng 👋

I build open-source guardrails for software delivery — linting, commit standards, and CI/CD automation.

If your pipeline checks C/C++ formatting or validates commit messages, there's a fair chance it already runs my code: cpp-linter runs in CI for 1,000+ public repositories, including projects from Apache, Samsung, Qualcomm, Bloomberg, LLNL, and Nextcloud, and commit-check is downloaded ~55k times a month from PyPI.

I'm an independent maintainer in Lithuania 🇱🇹, shipping on evenings and weekends, with no company behind any of it.

What you'd be sponsoring

  • cpp-linter — clang-format and clang-tidy on every pull request, posted back as inline review comments. Co-maintained with @2bndy5. See who uses it →
  • commit-check — commit message, branch naming, and AI-attribution rules for GitHub, GitLab, Bitbucket, and Jenkins.
  • Conventional Branch — a branch naming specification with a JSON Schema and conformance fixtures.
  • Open Delivery Spec — what I'm building now: delivery governance as evidence a machine can actually check.

Also explain-error-plugin (AI diagnosis of Jenkins build failures), jenkinsfilelint, gitstats, and mkdocs-ng, plus upstream contributions to Python and PyPA.

Where the money goes

  • Issues answered in days instead of months
  • Keeping up with upstream LLVM, Python, and Jenkins releases before they break your build
  • Domains and hosting, like conventionalbranch.org
  • Documentation that answers the question you actually have

Any amount helps

$1 a month puts your avatar on my sponsor wall. If one of these tools has saved your team an hour of debugging, it has already paid for a year of sponsorship.

Using these at work? Sponsor from your company's GitHub organization: it's billed to the org, and from $50 a month your logo goes in a project README. ❤️

Blog · Portfolio · PyPI · X

1 sponsor has funded shenxianpeng’s work.

@thnxdev

Featured work

  1. cpp-linter/cpp-linter-action

    A Github Action for linting C/C++ code integrating clang-tidy and clang-format to collect feedback provided in the form of file-annotations, thread-comments, workflow step-summary, and Pull Request…

  2. cpp-linter/cpp-linter-hooks

    C/C++ linter pre-commit hooks powered by clang-format and clang-tidy

    Python 50
  3. commit-check/commit-check

    Commit policy as code for teams and AI agents: commit messages, branch names, authors, sign-offs, tags, files and AI attribution, checked from one config file.

    Python 79
  4. commit-check/commit-check-action

    Commit policy as code on every pull request: the GitHub Action for Commit Check.

    Python 33
  5. conventional-branch/conventional-branch

    A specification for Git branch names — <type>/<description>, human-readable and machine-parseable. Ships a machine-readable spec, JSON Schema, and conformance fixtures.

    HTML 136
  6. jenkinsci/explain-error-plugin

    Explain Jenkins job failures with AI

    Java 46

Learn more about sponsoring developers and organizations.

Report abuse

Select a tier

$ a month

Choose a custom amount.

$1 a month

Select

👋 Hello World — the smallest way to say "this tool helped me."
✓ Your avatar on the sponsor wall in my GitHub profile README
✓ Earns you GitHub's Public Sponsor 🏅 achievement (sponsor publicly)
Every dollar counts. Thank you! ❤️

$5 a month

Select

☕ Coffee — one coffee a month keeps the late-night releases going.
Everything in 👋 Hello World, plus:
✓ Your name in the sponsor credits at the end of my blog posts

$50 a month

Select

🛡️ Guardrail · for companies — your team ships with these tools.
Everything in ☕ Coffee, plus:
✓ Your company logo (with link) in the README of the project you use
✓ Priority response on your issues and questions