Create SECURITY.md

[Amanyelmahdey]

Description

Documentation

Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.

[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

[greptile-apps]

Greptile Summary

This PR adds a SECURITY.md file to the repository, but it appears to be the unmodified GitHub template with placeholder content.

Critical Issues:

• Placeholder instructional text remains on lines 5-6 and 17-21 ("Use this section to tell people...")
• Version numbers (5.1.x, 5.0.x, 4.0.x) don't match the actual project version (8.7.0)
• No actual vulnerability reporting process is documented

The file needs to be customized with WorkOS-specific information before merging.

Confidence Score: 1/5

• This PR should not be merged as-is - it contains only placeholder content
• The SECURITY.md file is completely uncustomized from the GitHub template, with incorrect version numbers and no actual security reporting instructions, making it misleading for users trying to report vulnerabilities
• SECURITY.md requires complete rewrite with actual WorkOS security policy

Important Files Changed

Filename	Overview
SECURITY.md	Added GitHub SECURITY.md template without customization - contains placeholder text and incorrect version numbers

_{Last reviewed commit: efa4ca1}

[greptile-apps]

_{1 file reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Remove this placeholder instructional text

Suggested change

	Use this section to tell people about which versions of your project are
	currently being supported with security updates.

[greptile-apps]

Version numbers don't match the actual project version (currently 8.7.0 per package.json)

[greptile-apps]

Replace placeholder text with actual vulnerability reporting instructions (e.g., WorkOS security email, expected response time, etc.)

Suggested change

	Use this section to tell people how to report a vulnerability.
	Tell them where to go, how often they can expect to get an update on a
	reported vulnerability, what to expect if the vulnerability is accepted or
	declined, etc.
	To report a security vulnerability, please email security@workos.com with a detailed description of the issue. Our security team will respond within 48 hours to acknowledge receipt and provide next steps.