You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Audit redaction is top-level only; whitelisted fields like notes/bio persist PII verbatim #88
Why this matters now: The audit log is meant to be safe to retain; currently it can store raw user-entered PII (proof notes, bios) and nested objects unredacted.
Problem / What:redactDetails (audit.ts:56-68) only inspects top-level body keys against a whitelist. notes (proof.review / validator.review) and bio are whitelisted and stored verbatim; nested objects/arrays are not traversed for PII. The audit details column thus contains free-text PII.
Key Challenges: Defining a PII-safe redaction policy that also handles nested structures and known-sensitive fields, while preserving the operational value of the log.
Acceptance Criteria:
No raw free-text user input (notes, bio) is stored unredacted in AuditLog.details; nested PII is handled.
A test feeds PII-laden bodies and asserts redaction in the stored row.
Activity
aweledavid3 commentedon Aug 22, 2026
Hi maintainer I will like to work on this isssue
grantfox-oss commentedon Aug 22, 2026
🦊 GrantFox — @aweledavid3 has been assigned to this issue as part of the Third Campaign campaign!
Next steps:
Closes #88)Good luck! Track your progress on GrantFox.
grantfox-oss commentedon Aug 24, 2026
🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!
@aweledavid3's PR #96 was approved and merged by @cybermax4200.
🏆 @aweledavid3: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (344 total points). Track your full progress on GrantFox.
👏 Great work, @aweledavid3! Keep contributing to ecotask-network.
fix(audit): deep-redact PII fields in audit log (ecotask-network#96)