Only the latest commit on the main branch of this repository is supported for security updates.
| Version / Branch | Supported |
|---|---|
main |
✅ |
| Older commits | ❌ |
If you discover a security vulnerability or potential risk within this repository, please report it responsibly rather than opening a public issue.
- Go to the repository's Security tab on GitHub.
- Click Report a vulnerability to submit a private security advisory.
If GitHub Private Vulnerability Reporting is unavailable, please reach out via:
- Email: Private disclosure via contact details listed on kunalsuri.github.io or author profile.
When a vulnerability is reported:
- Acknowledgement: We aim to acknowledge receipt of the report within 48 hours.
- Assessment: The report will be reviewed and verified for impact.
- Resolution: If confirmed, a fix will be implemented and merged to
mainas quickly as possible. - Disclosure: Details of the vulnerability will be published after a fix has been deployed.
This repository enforces security best practices for static site delivery:
- Automated Code Analysis: CodeQL static analysis runs automatically on pushes and pull requests to
main. - Dependency Scanning: Dependabot automated security updates monitor npm dependencies for known vulnerabilities.
- Secret Scanning: GitHub Secret Scanning prevents accidental commits of sensitive credentials or API tokens.
- Static Hosting: The site is compiled to static HTML/CSS/JS via Astro and hosted on GitHub Pages with strict HTTPS enforcement.
- Blog & Source Code: Static source code is covered under Apache 2.0; content under CC BY 4.0.
- Third-Party Integrations: Commenting (Giscus) and analytics/search capabilities rely on client-side integrations with their respective privacy and security models.