Blazor-Server is pre-1.0 and releases a new v0.0.x version for every merged pull request.
Only the latest release is supported: security fixes land on main and ship in the next release, with no backports.
| Version | Supported |
|---|---|
Latest v0.0.x |
✅ |
| Any older release | ❌ |
Blazor-Server is a template for a server-rendered Blazor Web App; so far it holds the shared domain types (src/Domain).
The repository itself is protected as follows:
-
Secrets stay out of source control.
.envfiles are git-ignored at any depth. Local secrets belong in user secrets or.env. -
Keep Claude Code out of
.envfiles. The repo ships no Claude Code settings, since permissions are set per user (the repo-ci-baseline Template doesn't ship them either). Add these rules to your own~/.claude/settings.json, so Claude Code's file tools can't read or edit a.envunder the project a session runs in,.sandcastle/.envincluded:{ "permissions": { "deny": ["Read(**/.env)", "Read(**/.env.*)", "Edit(**/.env)", "Edit(**/.env.*)"] } }The
.env.*rules also hide committed.env.examplefiles, such as.sandcastle/.env.example; edit those by hand. The rules don't stop shell commands such ascat .env: deny those too, or turn on Claude Code's sandbox, if you need that. They cover sessions on your machine only. A Sandcastle sandbox starts with its own Claude Code settings, and it gets.sandcastle/.env's values as environment variables in any case. -
CodeQL analyzes the C# code and the GitHub Actions workflows whenever a pull request or push to
mainchanges them. -
Workflow hardening. Actions are pinned to commit SHAs, and
zizmorandactionlintcheck every workflow change. -
Dependabot proposes dependency updates after a seven-day cooldown, so a compromised release is usually caught upstream first.
-
Reviewed merges. A pull request merges only after its checks pass, Copilot has reviewed its head, and its review threads are resolved. One exception: once Copilot has reviewed three of a PR's commits, its own unresolved threads no longer hold the merge, so a PR can't chase new Copilot findings forever. Threads anyone else opens always do.
If you discover a security vulnerability in Blazor-Server, please report it responsibly:
Email: matthew.paulosky@outlook.com
Subject: [SECURITY] Blazor-Server Vulnerability Report
Please do NOT open a public GitHub issue for security vulnerabilities.
When reporting a security vulnerability, please include:
- Description - Clear description of the vulnerability
- Impact - Potential security impact and severity
- Steps to Reproduce - Detailed steps to reproduce the vulnerability
- Affected Versions - Which versions are affected
- Suggested Fix - If you have ideas for mitigation (optional)
- Your Contact Info - How we can reach you for follow-up
- Initial Response: Within 48 hours of report submission
- Status Update: Within 7 days with assessment and timeline
- Fix Timeline:
- Critical vulnerabilities: Within 7 days
- High severity: Within 14 days
- Medium/Low severity: Within 30 days
- We will work with you to understand and validate the vulnerability
- We will develop and test a fix before public disclosure
- We will credit you in the security advisory (unless you prefer anonymity)
- We request that you do not publicly disclose the vulnerability until we have released a fix
Security updates will be published:
- In the GitHub Security Advisories
- In the project CHANGELOG.md (if one exists)
- In release notes for security-related releases
When contributing to Blazor-Server, please follow these security guidelines:
- All code changes require review before merging
- Security-sensitive changes require additional scrutiny
- Never commit secrets, API keys, or passwords
- Add security-focused tests for authorization checks
- Test boundary conditions and edge cases
- Verify user isolation in integration tests
- Keep NuGet packages up to date
- Review dependency security advisories
- Use
dotnet list package --vulnerableto check for known vulnerabilities
- Use User Secrets for local development (
dotnet user-secrets) - Use Environment Variables for production
- Never commit
appsettings.Production.jsonwith secrets - Add sensitive files to
.gitignore
- Validate all user input in CQRS handlers
- Use parameterized queries (Entity Framework Core does this automatically)
- Sanitize data before rendering in Blazor components (Blazor does this automatically)
- OpenAI API calls - Notes content is sent to OpenAI for AI features (embeddings, summaries, tags)
- Local development - Uses SQL Server Express with Trusted Connection
- No rate limiting - Consider implementing rate limiting for production
- No audit logging - User actions are not currently logged
- Use HTTPS - Enable HTTPS and HSTS
- Secure connection strings - Use Azure Key Vault or similar
- Enable logging - Add security event logging
- Rate limiting - Implement API rate limiting
- Regular updates - Keep .NET and dependencies updated
- Security headers - Add security headers (CSP, X-Frame-Options, etc.)
- Monitor dependencies - Use GitHub Dependabot for security alerts
Thank you for helping keep Blazor-Server secure!