Fix references to Template DotNet Tool in documentation files

Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>

Author: Copilot

.yamllint.yaml

@@ -1,5 +1,5 @@
 ---
-# yamllint configuration for SarifMark
+# yamllint configuration for Template DotNet Tool
 # This configuration defines the rules for YAML file linting
 
 extends: default

CODE_OF_CONDUCT.md

@@ -131,4 +131,4 @@ For answers to common questions about this code of conduct, see the FAQ at
 [Mozilla CoC]: https://github.com/mozilla/diversity
 [FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations
-[issues]: https://github.com/demaconsulting/SarifMark/issues
+[issues]: https://github.com/demaconsulting/TemplateDotNetTool/issues

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to SarifMark
+# Contributing to Template DotNet Tool
 
-Thank you for your interest in contributing to SarifMark! We welcome contributions from the community and appreciate
+Thank you for your interest in contributing to Template DotNet Tool! We welcome contributions from the community and appreciate
 your help in making this project better.
 
 ## Code of Conduct
@@ -18,7 +18,7 @@ If you find a bug, please create an issue on GitHub with the following informati
 - **Steps to Reproduce**: Detailed steps to reproduce the issue
 - **Expected Behavior**: What you expected to happen
 - **Actual Behavior**: What actually happened
-- **Environment**: Operating system, .NET version, SarifMark version
+- **Environment**: Operating system, .NET version, Template DotNet Tool version
 - **Logs**: Any relevant error messages or logs
 
 ### Suggesting Features
@@ -56,8 +56,8 @@ We follow a standard GitHub workflow for contributions:
 1. Clone the repository:
 
    ```bash
-   git clone https://github.com/demaconsulting/SarifMark.git
-   cd SarifMark
+   git clone https://github.com/demaconsulting/TemplateDotNetTool.git
+   cd Template DotNet Tool
    ```
 
 2. Restore dependencies:
@@ -253,7 +253,7 @@ When creating a pull request, include:
 
 ## Requirements Management
 
-SarifMark uses [DemaConsulting.ReqStream][reqstream] for requirements traceability:
+Template DotNet Tool uses [DemaConsulting.ReqStream][reqstream] for requirements traceability:
 
 - All requirements are defined in `requirements.yaml`
 - Each requirement should be linked to test cases
@@ -278,14 +278,14 @@ Releases are managed by project maintainers. The process includes:
 
 ## License
 
-By contributing to SarifMark, you agree that your contributions will be licensed under the MIT License.
+By contributing to Template DotNet Tool, you agree that your contributions will be licensed under the MIT License.
 
-Thank you for contributing to SarifMark!
+Thank you for contributing to Template DotNet Tool!
 
-[code-of-conduct]: https://github.com/demaconsulting/SarifMark/blob/main/CODE_OF_CONDUCT.md
+[code-of-conduct]: https://github.com/demaconsulting/TemplateDotNetTool/blob/main/CODE_OF_CONDUCT.md
 [dotnet-download]: https://dotnet.microsoft.com/download
 [csharp-conventions]: https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions
 [reqstream]: https://github.com/demaconsulting/ReqStream
-[discussions]: https://github.com/demaconsulting/SarifMark/discussions
-[issues]: https://github.com/demaconsulting/SarifMark/issues
-[security]: https://github.com/demaconsulting/SarifMark/blob/main/SECURITY.md
+[discussions]: https://github.com/demaconsulting/TemplateDotNetTool/discussions
+[issues]: https://github.com/demaconsulting/TemplateDotNetTool/issues
+[security]: https://github.com/demaconsulting/TemplateDotNetTool/blob/main/SECURITY.md

SECURITY.md

@@ -11,7 +11,7 @@ We release patches for security vulnerabilities in the following versions:
 
 ## Reporting a Vulnerability
 
-We take the security of SarifMark seriously. If you believe you have found a security vulnerability, please report it
+We take the security of Template DotNet Tool seriously. If you believe you have found a security vulnerability, please report it
 to us as described below.
 
 ### How to Report
@@ -60,31 +60,31 @@ Security updates will be released as:
 
 ## Security Best Practices
 
-When using SarifMark, we recommend following these security best practices:
+When using Template DotNet Tool, we recommend following these security best practices:
 
 ### Input Validation
 
 - Validate SARIF analysis tools API responses before processing
 - Be cautious when processing data from untrusted sources
-- Use the latest version of SarifMark to benefit from security updates
+- Use the latest version of Template DotNet Tool to benefit from security updates
 
 ### Dependencies
 
-- Keep SarifMark and its dependencies up to date
+- Keep Template DotNet Tool and its dependencies up to date
 - Review the release notes for security-related updates
 - Use `dotnet list package --vulnerable` to check for vulnerable dependencies
 
 ### Execution Environment
 
-- Run SarifMark with the minimum required permissions
-- Avoid running SarifMark as a privileged user unless necessary
+- Run Template DotNet Tool with the minimum required permissions
+- Avoid running Template DotNet Tool as a privileged user unless necessary
 - Validate API tokens and credentials are stored securely
 
 ## Known Security Considerations
 
 ### API Integration
 
-SarifMark integrates with SARIF analysis tools APIs. Users should:
+Template DotNet Tool integrates with SARIF analysis tools APIs. Users should:
 
 - Protect API tokens and credentials
 - Use HTTPS connections to SARIF analysis tools
@@ -93,7 +93,7 @@ SarifMark integrates with SARIF analysis tools APIs. Users should:
 
 ### File System Access
 
-SarifMark reads and writes files on the local file system. Users should:
+Template DotNet Tool reads and writes files on the local file system. Users should:
 
 - Ensure appropriate file permissions are set on output files
 - Be cautious when processing files in shared directories
@@ -116,7 +116,7 @@ We will credit security researchers who report vulnerabilities responsibly. If y
 
 ## Third-Party Dependencies
 
-SarifMark relies on third-party packages. We:
+Template DotNet Tool relies on third-party packages. We:
 
 - Regularly update dependencies to address known vulnerabilities
 - Use Dependabot to monitor for security updates
@@ -141,9 +141,9 @@ For general bugs and feature requests, please use [GitHub Issues][issues].
 - [.NET Security Best Practices][dotnet-security]
 - [GitHub Security Advisories][security-advisories]
 
-Thank you for helping keep SarifMark and its users safe!
+Thank you for helping keep Template DotNet Tool and its users safe!
 
-[security-advisories]: https://github.com/demaconsulting/SarifMark/security/advisories
-[issues]: https://github.com/demaconsulting/SarifMark/issues
+[security-advisories]: https://github.com/demaconsulting/TemplateDotNetTool/security/advisories
+[issues]: https://github.com/demaconsulting/TemplateDotNetTool/issues
 [owasp-practices]: https://owasp.org/www-project-secure-coding-practices-quick-reference-guide/
 [dotnet-security]: https://learn.microsoft.com/en-us/dotnet/standard/security/