Skip to content
Either running or coding.
Either running or coding.


@sindresorhus @kpcyrd @denisse-dev


@PyCQA @keylime @sigstore
Block or Report

Block or report lukehinds

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Luke Hinds

I am software engineer working mostly on open source security projects. I have lots of experience bootstrapping projects from new and helping grow diverse, inclusive and friendly 👯 communitees.

I founded project sigstore and developed the keylime project alongside MIT lincoln labs.

I also do a fair number of gigs around open source security in general.

You can find me on twitter @decodebytes, or linkedin

I currently work @ Red Hat in the CTO Office as the security engineering lead.

I am always happy to 💬 about software security and growing open source communities.

Analytics ⚙️

Github Statistics


  1. Sigstore OIDC PKI

    Go 354 69

  2. Software Supply Chain Transparency Log

    Go 556 104

  3. Common go library shared across sigstore services and clients

    Go 301 65

  4. A CNCF Project to Bootstrap & Maintain Trust on the Edge / Cloud and IoT

    Python 259 99

1,345 contributions in the last year

Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Mon Wed Fri

Contribution activity

August 2022

Created 2 repositories

Created a pull request in sigstore/TSC that received 6 comments

Add Trevor Rosen and Santiago Torres-Arias to TSC

Signed-off-by: Luke Hinds Summary Release Note Documentation

+2 −0 6 comments
Opened 6 other pull requests in 2 repositories
Reviewed 7 pull requests in 5 repositories
sigstore/TSC 2 pull requests
sigstore/community 2 pull requests
sigstore/ruby-sigstore 1 pull request
keylime/keylime 1 pull request
sigstore/sigstore-website 1 pull request

Created an issue in sigstore/cosign that received 9 comments


A few users are being tripped up on this subject env not being documented. There should be an entry in


Seeing something unexpected? Take a look at the GitHub profile guide.