Auditing logs
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 138
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
cbft needs to write significant events to the audit log
Contributor guide
No contributing guide indexed for this repository
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 no files, tests, or entry points. Start by reviewing cbft's existing logging and event paths, then determine which significant events require audit records and how completion will be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100