Skip to content

Add security policy (SECURITY.md) #306

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
level09 merged 1 commit into from
Apr 10, 2026
Merged

Add security policy (SECURITY.md) #306

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
34 changes: 34 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# Security Policy

## Reporting a Vulnerability

If you discover a security vulnerability in Bayanat, please report it through [GitHub's private vulnerability reporting](https://github.com/sjacorg/bayanat/security/advisories/new).

Do not open a public issue for security vulnerabilities.

## What to Include

- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)

## Response

We will acknowledge receipt within 72 hours and provide an initial assessment within 7 business days.

## Supported Versions

| Version | Supported |
|---------|-----------|
| 3.x | Yes |
| < 3.0 | No |

## Security Practices

- Static analysis via Semgrep and CodeQL
- Dependency scanning via pip-audit and retire.js
- Pre-commit secret scanning via Gitleaks
- GitHub secret scanning with push protection
- Signed commits enforced on protected branches
- Comprehensive [threat model](docs/security/threat-model.md)
Loading