Skip to content

fix: Shared Team Inbox - Security and performance hardening - #1897

Open
wolfyres wants to merge 8 commits into
Stellar-Mail:mainfrom
wolfyres:fix/issue-447
Open

fix: Shared Team Inbox - Security and performance hardening#1897
wolfyres wants to merge 8 commits into
Stellar-Mail:mainfrom
wolfyres:fix/issue-447

Conversation

@wolfyres

Copy link
Copy Markdown

Summary

Add safety, sanitization, and performance constraints for the Shared Team Inbox tool as required by #447.

Closes #447

Deliverables & Changes

  • Threat Model & Performance Docs: Added SECURITY.md and PERFORMANCE.md within the tool directory detailing payload limits, threat vectors, and mitigation rules.
  • Validation & Sanitization (utils/): Added schema checkers (validateSharedMessage), XSS stripping (sanitizeMessageBody), and header/filename sanitization.
  • Performance Constraints (utils/performance.ts): Implemented page-size bounding (max 50 per page) and body length truncation for large messages (>100KB).
  • Hooks & Boundary Components: Created useSharedInboxSafety and SharedInboxGuard to render safe message feeds without risk of UI crashes or scripting attacks.
  • Unit Testing: Added isolated unit tests in tools/v1/team/shared-team-inbox/__tests__/safety.test.ts.

Strict Scope Verification

  • All file additions/modifications are strictly contained inside tools/v1/team/shared-team-inbox/.
  • Zero modifications made to app shell, dashboard, auth, routing, design system, or core database/Stellar integrations.
  • Local unit tests passing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[V1][team] Shared Team Inbox - Security and performance hardening

1 participant