Audit logs
Open
Nobody has claimed this yet.
TBD/Design/Discussion phase
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
Subscribers may want audit logs of sensitive operations:
- logins
- adding users to accounts
- CRUD on tasks
- CRUD on paired aggregators
We should emit audit logs that note what user did this and perhaps things like IP address or a geolocation.
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
Start by locating the entry points for logins, account membership changes, task CRUD, and paired-aggregator CRUD, then review any existing logging. Define which audit events and metadata, such as IP address or geolocation, are required. Done means the agreed sensitive operations emit auditable records with documented fields and coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100