Security fixes are provided for the latest stable ChangeMe template release published from this repository. Older template versions and forks generated with dotnet new changeme are maintained by their owners.
| Version | Supported |
|---|---|
Latest ChangeMe NuGet release |
Yes |
| Older template releases | Best effort |
| Generated applications | Maintained by the project that scaffolded them |
Do not open a public GitHub issue for security reports.
Preferred channel:
- Open a private security advisory on this repository, or
- Email the maintainer listed in
LICENSEwith the subject prefix[ChangeMe security].
Include:
- Affected component (template source, sample app, deployment scripts, documentation, etc.)
- Steps to reproduce or proof-of-concept
- Impact assessment (confidentiality, integrity, availability)
- Affected version or commit SHA when known
You should receive an acknowledgment within 7 days. We will coordinate disclosure timing with you before publishing a fix or advisory.
- Vulnerabilities in third-party dependencies already tracked by Dependabot — report upstream or wait for the weekly dependency PR unless exploitability in this template is demonstrated.
- Deployments you operate outside the documented Ansible/GitLab flow (custom secrets handling, public Swagger/Hangfire exposure, etc.) unless the template defaults are unsafe without extra configuration.
- Issues in generated applications that changed template defaults or removed documented hardening.
Review before production:
- Keep
SwaggerOptions:EnabledandHangfireOptions:DashboardEnableddisabled outside Development. - Replace all placeholder secrets in
.env, GitLab variables, and VPSsecrets.env. - Use protected GitLab environments and SSH file variables for deployment keys (deployment).