[hilaryy82-source]

closes #556

Pull Request

Summary

Related Issue

Closes #

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactor / chore

Checklist

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings or errors.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• All CI checks pass (lint, build, tests, type checks).
• Any dependent changes have been merged and published.

Security Checklist

• No secrets, credentials, tokens, or API keys are logged, persisted, or transmitted.
• No sensitive data is written to logs, error messages, or telemetry.
• Content Security Policy (CSP) remains intact and has not been weakened.
• No new external dependencies introduce known vulnerabilities.
• Input validation and output encoding are applied to untrusted data.
• Authentication and authorization checks are preserved and correctly enforced.
• No use of unsafe APIs (e.g., eval, innerHTML, dangerouslySetInnerHTML) without justification.
• Changes have been reviewed for potential injection, XSS, CSRF, and SSRF risks.

Screenshots / Additional Context

[vercel]

Someone is attempting to deploy a commit to the paps' projects Team on Vercel.

A member of the Team first needs to authorize it.