Open-source contributions as evidence — what actually made mine credible

My work is heavily open-source, and I wasn't sure at first how to translate "I maintain a widely-used library" into something that reads as formal evidence rather than just a claim. Sharing what actually worked. Concrete, verifiable metrics mattered a lot: adoption numbers (downloads, dependent projects, stars — with the caveat that these numbers need context, since raw counts alone don't establish significance the way a citation count alone doesn't), a clear description of my specific role (maintainer, primary author, core contributor — precision matters here, since "contributor" can mean very different levels of involvement), and independent evidence of the project's standing in its ecosystem (mentions in industry articles, talks referencing it, other significant projects depending on it). What helped make it credible rather than just impressive-sounding: being precise and honest about my actual role, rather than inflating a moderate contribution into something bigger. A reviewer who can verify the project (open source is, by definition, checkable) will notice if the claimed role doesn't match what's publicly visible in the project's own history.