The DevImpact CLI securely connects your local GitHub activity to the DevImpact dashboard. It uses your local GitHub authentication (via the GitHub CLI) and only accesses the repositories you explicitly provide.
npm install @devimpact/cliThe DevImpact CLI securely connects your local GitHub activity to the DevImpact dashboard.
It uses your local GitHub authentication (via the GitHub CLI) and only accesses the repositories you explicitly provide.
Before installing, make sure you have:
ā¢ Node 18+
ā¢ GitHub CLI (gh) installed and authenticatedgh auth status
Install globally from npm
``sh`
npm install -g @devimpact/cli
Verify installation
`sh`
devimpact --version
1. Go to your DevImpact account and generate a CLI token.
2. Run:
`sh`
devimpact init --cli-token
This securely links your CLI to your DevImpact account.
The token is hashed locally and never stored in plain text.
Use the sync command to fetch GitHub pull request data and push it to your DevImpact account:
`sh`
devimpact sync
You can provide repositories manually if you only want to sync those
`sh`
devimpact sync --repo org/frontend --repo org/api --repo org/mobile
The CLI uses your local GitHub CLI authentication, so DevImpact never sees your PAT or OAuth token.
When you run devimpact sync:
1. It uses your existing gh auth session to call gh api on your machine.
2. It only accesses the repos you explicitly pass
3. It fetches metadata about your PRs, reviews, commits, and files
for the repos you specify.
4. It strips diffs, commit messages, and code blocks from data.
5. It sends a sanitized JSON payload to the DevImpact backend
to power your personal dashboard.
No other GitHub data is accessed.
š For a detailed list of APIs and fields, see DATA & SECURITY.
You can inspect or delete your local DevImpact config at:
`sh`
~/.devimpact/config.json
To remove the CLI:
`sh``
npm uninstall -g @devimpact/cli
MIT