Skip to content

docs: add security policy and list runtime dependencies in NOTICE #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
drkjc merged 2 commits into from
Oct 14, 2026
Merged

docs: add security policy and list runtime dependencies in NOTICE #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
79e15ae
docs: add security policy
drkjc Oct 14, 2026
988e230
docs: list runtime dependencies and licenses in NOTICE
drkjc Oct 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions NOTICE
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,12 @@
Spreedly Composer Python Server SDK
Copyright 2025-2026 Spreedly, Inc.

This SDK depends on the following packages at runtime. pip installs them
alongside the SDK; they are not bundled with it. Full license texts are in
THIRD-PARTY-LICENSES.

- requests (Apache-2.0)
- urllib3 (MIT)
- idna (BSD-3-Clause)
- charset-normalizer (MIT)
- certifi (MPL-2.0)
36 changes: 36 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
# Security Policy

## Reporting Security Vulnerabilities

Spreedly takes security seriously and appreciates your help in keeping our products and services secure. If you discover a security vulnerability in this repository, please report it to us using one of the following methods. **Do not** open a public GitHub issue, pull request, or discussion describing the vulnerability.

### Option 1: Spreedly Help Center

Submit a security vulnerability report through the [Spreedly Help Center](https://spreedly.com/support/) by submitting a request to Customer Support. This will open a support ticket for you, allowing you to securely communicate with our security team.

### Option 2: Spreedly Security Team

Email our security team directly at **security@spreedly.com** with details about the vulnerability you've discovered.

## What to Include in Your Report

When reporting a security vulnerability, please include:

- A clear description of the vulnerability
- Steps to reproduce the issue
- Potential impact of the vulnerability
- Any suggested fixes or mitigations (if available)

## Response Timeline

We will acknowledge receipt of your report within 48 hours and provide an initial assessment within 5 business days. We'll keep you informed of our progress as we work to address the issue.

## Disclosure Policy

We ask that you:

- Allow us a reasonable amount of time to address the vulnerability before public disclosure
- Act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services
- Not access or modify data that does not belong to you

Thank you for helping keep Spreedly and our customers secure.
Loading