Smart Campus AI takes security seriously. This document describes how to report vulnerabilities and what you can expect from us in return.
| Version | Supported |
|---|---|
| main | β Fully supported |
Currently the project is in active development. All fixes are applied to main
and released as updates to the deployed demo.
Please do NOT open a public issue for security vulnerabilities.
Instead, report it privately:
- GitHub Private Vulnerability Reporting β use the Security Advisories tab on the repository (preferred), or
- Email the maintainer β reach out via the contact details on the GitHub profile.
To help us triage quickly, please include:
- Affected component β web app, mobile app, Supabase/DB, auth, chatbot, etc.
- Description β what the vulnerability is and how it can be exploited
- Steps to reproduce β a small, self-contained example
- Impact β what an attacker could gain
- Suggested fix (optional but appreciated)
- You will receive an acknowledgment within 48 hours
- We will investigate and keep you updated on progress
- We will coordinate a fix and, where appropriate, credit you in the changelog
- We will not pursue legal action for good-faith reports made in accordance with this policy
- Never commit secrets β keys live in
.env.*files which are git-ignored - Environment variables β all sensitive configuration is injected at runtime
- Supabase RLS β Row-Level Security policies gate every table access
- Service-role key β used only in trusted, server-side environments, never exposed to the browser
- Server-side validation β admin routes re-validate roles on the server
- HTTPS/TLS β all traffic is encrypted in transit
In-scope: the repositories and deployed demos owned by the project.
Out-of-scope: third-party services you connect (Supabase, Groq, Vercel) β report issues to those vendors directly.