Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Ruby b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
Update Security policies around AI-generated submissions
Damian Legawiecab5b78122f73
diff --git a/.github/SECURITY.md b/.github/SECURITY.mdindex cc19f8c480..5df4752197 100644--- a/.github/SECURITY.md+++ b/.github/SECURITY.md@@ -4,10 +4,10 @@The following versions are actively maintained and receive security patches.-| Version | Release date | End of life |-| ------- | ------------ | ----------- |-| 5.0 | 26.03.2025 | 26.03.2028 |-| 4.10 | 06.09.2024 | 06.09.2027 |+| Version | End of life |+| ------- | ------------ |+| 5.x | 26.03.2028 |+| 4.10 | 06.09.2027 |Versions that are not listed above will not receive any security patches or fixes.@@ -19,12 +19,32 @@ Instead, please send an email to [[email protected]](mailto:security@spPlease include as much of the following information as possible to help us triage your report:-- Type of vulnerability (e.g. SQL injection, XSS, CSRF, etc.)+- Type of vulnerability (e.g., SQL injection, XSS, CSRF, etc.)- Affected version(s)- Step-by-step instructions to reproduce the issue- Proof of concept or exploit code (if available)- Impact assessment of the vulnerability+### Automated Reports++We do not accept:++- Low-effort or automatically generated reports (including AI-generated content)+- Reports that are bulk-submitted without context or verification+- Reports that do not address feedback or questions+- Reports not tested against the current edge version from GitHub++You should:++- Clearly disclose if you used AI to create the vulnerability report.+ This ensures transparency and accountability.+- Explicitly confirm that you manually verified the findings and the contents.+ Reports that were not manually verified may be get rejected without follow-ups.++### No Monetary Rewards++We do not have a bounty program in place, so we cannot offer monetary rewards for any reported problems.+### Submitting a PatchIf you would like to provide a patch yourself for the security issue **do not open a pull request for it**. Instead, create a commit on your fork of Spree and run this command:@@ -37,8 +57,8 @@ Email a description of the patch along with the `patch.txt` file to [security@sp### Disclosure Process-1. Security report is received and acknowledged within **48 hours**.-2. The issue is confirmed and a severity level is assigned.+1. Security report is received and acknowledged within **72 hours**.+2. The issue is confirmed, and a severity level is assigned.3. A fix is developed and tested against all supported versions.4. A new release is published with the fix and a [GitHub Security Advisory](https://github.com/spree/spree/security/advisories) is created.5. Reporter is credited in the advisory (unless anonymity is requested).@@ -49,4 +69,4 @@ Published security advisories can be found at [GitHub Security Advisories](https## More Information-For detailed security documentation including best practices and enterprise security features, see the [Spree Security Documentation](https://spreecommerce.org/docs/developer/security/security_policy).+For detailed security documentation, including best practices and enterprise security features, see the [Spree Security Documentation](https://spreecommerce.org/docs/developer/security/security_policy).