commit-stream v0.3.1 releases: drinks commit logs from the Github event
Commit Stream
commit-stream drinks commit logs from the Github event firehose exposing the author details (name and email address) associated with Github repositories in real-time.
OSINT / Recon uses for Redteamers / Bug bounty hunters:
- Uncover repositories which employees of a target company is committing code (filter by email domain)
- Identify repositories belonging to an individual (filter by author name)
- Chain with other tools such as trufflehog to extract secrets in uncovered repositories.
Changelog v0.3.1
- Slack and database support
Download
Use
commit-stream requires a Github personal access token to be used. You can generate a token navigating in Github [Settings / Developer Settings / Personal Access Tokens] then selecting ‘Generate new token’. Nothing here needs to be selected, just enter the name of the token and click generate.
Once the token has been created, the recommended method is to set it via an environment variable CSTREAM_TOKEN:
export CSTREAM_TOKEN=xxxxxxxxxx
Alternatively, the –token switch may be used when invoking the program, e.g:
./commit-stream --token xxxxxxxxxx
When running commit-stream with no options, it will immediately dump author details and the associated repositories in CSV format to the terminal. Filtering options are available.
To filter by email domain:
./commit-stream --email '@company.com'
To filter by author name:
./commit-stream --name 'John Smith'
Multiple keywords can be specified with a , character. e.g.
./commit-stream --email '@telsa.com,@ford.com'
It is possible to search up to 20 previous commits for the filter keywords by specifying –all-commits. This may increase the likelihood of a positive matches.
Email addresses that have been set to private (@users.noreply.github.com) can be committed by specifying –ignore-priv. This is useful to reduce the volume of data collected if running the tool for an extended period of time.
Copyright (c) 2020 @x1sec
Source: https://github.com/x1sec/