NixOS / NixOS/nix-security-tracker
GitHub independence
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 116
- Forks
- 41
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 70
Description
This issue is not in the scope of our paid work and sprints.
Currently, we have GitHub dependencies in two forms:
- OAuth 2 connector
- Foreign entities who are allowed to perform actions (security team, etc.)
We can generalize the OAuth 2 connector properly without too much issue.
For foreign entities, we can move this problem to a generic userinfo request to analyze the roles and scopes which are bestowed upon someone.
We probably need to introduce some error handling to automatically disable some of the GitHub features if you are running with another forge.
At the same time, a trivial implementation would be the DevelopmentDirectory where we can make up whatever we want.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the OAuth 2 connector, generic userinfo request, and DevelopmentDirectory as starting points; locate these components and the current GitHub-specific foreign-entity handling. Map the roles, scopes, and dependent features, then establish what must work with another forge and which GitHub features should be disabled when unsupported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- authentication, authorization, backend, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100