ChainJacking is a tool to find which of your Go lang direct GitHub dependencies is susceptible to ChainJacking attack. Read more about it here
Requirements
- Python 3.6+ and pip
- Go and it's binaries >= 1.13
- GitHub token (for API queries)
-
💡 This token is used for read only purposes and does not require any permissions
-
Installation
pip install chainjacking
Using in CI Workflows
ChainJacking can be easily integrated into modern CI workflows to test new code contributions.
GitHub Actions
ci-example.mp4
Example configuration:
name: Pull Request
on:
pull_request
jobs:
build:
name: Run Tests
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/[email protected]
- uses: actions/[email protected]
with:
python-version: '3.9'
- name: ChainJacking tool test
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
python -m pip install -q chainjacking
python -m chainjacking -gt $GITHUB_TOKEN
CLI
ChainJacking module can be run as a CLI tool simply as
python -m chainjacking
CLI Arguments
-gt- GitHub access token, to run queries on GitHub API (required)-p- Path to scan. (default=current directory)-v- Verbose output mode-url- Scan one or more GitHub URLs-f- Scan one or more GitHub URLs from a file separated by new-line
Example: Scan a Go project
navigate your shell into a Go project's directory, and run:
python -m chainjacking -gt $GH_TOKEN
28 Oct 31, 2022
1 Feb 7, 2022
101 Dec 20, 2022
253 Jan 5, 2023
42 Dec 29, 2022
1 Jun 15, 2022
4 Dec 12, 2022
19 Dec 26, 2022
1 Nov 5, 2021
1 Jul 13, 2022
3 Nov 28, 2021
61 Oct 08, 2022
2 Apr 22, 2022
9.5k Jan 09, 2023
2 Feb 04, 2022
1 Dec 06, 2021
4 Jun 13, 2021
3 Apr 13, 2022
5 Oct 22, 2021
1 Jan 08, 2022
10 Aug 19, 2022
2 Dec 09, 2021
1 Jul 22, 2022
17 Nov 29, 2022
2 May 01, 2022
1 Feb 10, 2022
35 Dec 24, 2022
1 Dec 31, 2021
1 Feb 09, 2022