ivx research

ivx research Difflicit GitHub

GitHub

A published analysis is a GitHub repository with an analysis.json naming its project. Difflicit reads public ones without any account. Connect GitHub to:

  • see your own analyses, private ones included;
  • Get a copy: fork the published analysis, or create your own repository for a project;
  • raise GitHub's limit of 60 anonymous requests an hour.

Sign in with ivx

On ivx instances such as ivx/xnu, Sign In uses your ivx account at iam.ivx.run (OAuth, so Difflicit never sees your password). GitHub is then used through iam: your GitHub token stays with iam and never reaches Difflicit or your browser.

On your ivx account page you choose what ivx apps may do with GitHub: public repositories only, or public and private. GitHub can't limit access to particular repositories, so pick public only unless you keep private analyses. Even then, apps may only read, fork, and create repositories named like a CVE (CVE-2024-54494, what Get a copy creates); nothing else is passed through. Revoke Difflicit there at any time, and it's signed out everywhere.

In the desktop app, Sign In opens your browser and returns to the app when you're done. Cloning private repositories still uses your own git credentials, since the app never holds a GitHub token.

Bring your own token

Instances without ivx accounts ask for a GitHub personal access token instead (Connect GitHub). It's kept in your browser and sent only to api.github.com. Remove it from the same dialog. Give it the repo scope for private analyses, or public_repo for public ones only.

Where analyses live

A project's analyses are found by name: each instance has a naming convention (on ivx/xnu, a repository named after the CVE, such as CVE-2024-54494). The published analysis is the one in the instance's organization (ivxlabs on ivx/xnu). Yours is a fork of it, or a repository of the same name in your account. When you've improved a fork, Create pull request offers your changes back.

A repository only counts as an analysis when its analysis.json names the project, so a same-named repository that isn't one is ignored.