SECURITY.md

main 1.5 KB · 28 lines · markdown

1	# Security policy
2
3	OpenVibe is run in the open, and we want to hear about security problems before anyone else does.
4
5	## Reporting a vulnerability
6
7	Email [email protected] with "security" in the subject. Please include what you found, where (URL,
8	repository, file), how to reproduce it, and what an attacker could do with it. Do not open a public GitHub issue for
9	a vulnerability, and do not test against other people's accounts, data or streams.
10
11	We reply within 7 days, keep you updated while we fix it, and credit you when the fix ships if you would like.
12
13	## Scope
14
15	Every OpenVibe service and site (openvibe.live, openvibe.network, openvibe.tools, openvibe.media, openvibe.community,
16	openvibe.games and the other openvibe.* domains) and every repository under github.com/OpenVibers. Machine-readable
17	contact details are at `/.well-known/security.txt` on each site.
18
19	For OpenVibe.Report specifically: the service reads Network, Live and Billing over loopback, keeps its own
20	analytics tables (counts and public channel facts only; no money payloads), and has no accounts. The interesting
21	surface is the path parameters it forwards (validated before a request), the HTML it renders (every source text is
22	escaped by `server/views/index.js`), the `/internal/` routes (loopback-only; `POST /internal/events` verifies the
23	Events v2 HMAC) and the origins and service token it is configured with. A Billing or Events secret is never logged.
24
25	## Supported versions
26
27	Only the current `main` branch, which is what runs in production, receives fixes.
28