aquasecurity / aquasecurity/tracee
Create a triggerEvents package and cleanup tracee.go
Open
kind/chore
priority/backlog
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 507
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
## Description
The uprobe triggering logic added to tracee.go should go into its own package and tracee.go should be refactored/cleaned.
## Output of `tracee -v`:
```
v0.13.0
```
Contributor guide
Research direction
Start by locating the uprobe triggering logic in tracee.go and map the code that should move into the new triggerEvents package. Refactor tracee.go around that boundary while preserving the existing behavior, then run the tracee -v entry point and the project's relevant checks to confirm the refactor is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100