feature: github event logging
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 305
- Forks
- 148
- Avg merge
- 9h 2m
- Merged PRs (30d)
- 3
Description
Read all events from github (from commits to pushes to merges to acl, etc) and store them in a database for later use. The idea here is to be able to:
- investigate security incidents (audits -- warn on force pushes, suspicious activity, etc)
- show interesting statistics, perhaps even part of nodejs.org (pushes day/interesting people/new joins/etc)
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
No files, tests, or entry points are named. Start by surveying the repository and its GitHub integration to determine which event sources and database facilities exist; done would mean reliably collecting the requested GitHub activity for later security audits and statistics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript, node.js
- Domain
- analytics, backend, databases, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100