Skip to content

docs: add a security policy (SECURITY.md) - #36

Merged
homer6 merged 1 commit into
devfrom
docs/security-policy
Nov 16, 2026
Merged

homer6 merged 1 commit into
devfrom
docs/security-policy

Conversation

@homer6

@homer6 homer6 commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

What: A security policy: how to report a vulnerability privately, and what we commit to.
Why: G1 of the open-source release (https://github.com/oramasearch/orama-bridge/issues/273): every released repo needs one. Steve chose the address and targets on 2026-11-14.
How: One new file, the same in every repo.

Private reporting to security@orama.com, with response targets of 2 business days, 7 days and 90 days. G1 of oramasearch/orama-bridge#273.
@homer6

homer6 commented Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

Merged into dev as a merge commit (37dec34c) on Steve's review (2026-11-15). Low risk, on Steve's 2026-11-15 instruction to merge the low-risk PRs. Not built or tested in review (tests run at the release cut).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant