Merge pull request #1 from Tirsvad/main

Initial

Author: Tirsvad

.gitignore

@@ -416,3 +416,4 @@ FodyWeavers.xsd
 *.msix
 *.msm
 *.msp
+/tests/test-results.xml

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+tirsvadweb@gamil.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,75 @@
+# Contributing to VSSolution Creation Script
+
+Thank you for your interest in contributing! Your help is greatly appreciated.  
+This document outlines the process for contributing to the project.
+
+## Coding Guidelines
+
+This project uses PowerShell for scripting. Follow these PowerShell-specific guidelines:
+
+- Follow PowerShell best practices and the PowerShell Style Guidelines.
+- Use approved verbs for functions (see `Get-Verb`) and choose clear, descriptive function names.
+- Prefer advanced functions with `CmdletBinding()` so common parameters and `-Verbose`/`-Debug` are available.
+- Use strong typing and parameter validation attributes (`[Parameter()]`, `ValidateSet`, `ValidateNotNullOrEmpty`, etc.).
+- Support pipeline input for functions where appropriate and implement `Begin/Process/End` blocks when processing pipeline input.
+- Provide comment-based help for all public functions and scripts (examples, parameters, outputs).
+- Avoid aliases and use full cmdlet names in committed code (aliases are fine interactively).
+- Use `ShouldProcess`/`-WhatIf` for destructive operations and honor `-Confirm` when appropriate.
+- Use `Try/Catch` for error handling and throw or `Write-Error` as appropriate; prefer terminating errors when callers must act on failures.
+- Use `Write-Verbose`, `Write-Debug`, `Write-Warning`, and `Write-Error` for structured output and logging; do not write unstructured progress to stdout.
+- Keep formatting consistent (4-space indentation is recommended), avoid global variables, and keep functions focused and small.
+- Use `PSScriptAnalyzer` to lint scripts and address reported issues. Include a baseline or configuration if needed.
+- Organize modules with a `.psm1` and `.psd1` manifest; explicitly export public functions with `Export-ModuleMember`.
+- Write unit tests with `Pester` and place tests under a `tests/` folder. Run tests locally and in CI.
+- Avoid hard-coded credentials/secrets; use secure methods (secure strings, environment variables, or secret stores).
+- Use semantic versioning for modules and include a changelog for releases.
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+- Open an issue on [GitHub Issues](https://github.com/TirsvadScript/PS.Logging/issues).
+- Use a clear and descriptive title.
+- Include steps to reproduce, expected and actual behavior, and environment details.
+
+### Suggesting Enhancements
+
+- Open an issue and label it as an enhancement.
+- Clearly describe the feature, why it would be useful, and any ideas for implementation.
+
+### Pull Requests
+
+1. **Fork the repository** and clone it locally.
+2. **Create a new branch** for your feature or fix
+```
+git checkout -b feature/YourFeatureName
+```
+
+3. **Make your changes** with clear, concise commits.
+4. **Write or update tests** as needed.
+5. **Ensure all tests pass** before submitting.
+6. **Push to your fork** and submit a pull request to the `main` branch.
+7. **Describe your changes** in the pull request and reference any related issues.
+
+### Code Style
+
+- Follow the existing code style and conventions.
+- Use meaningful names and XML documentation where appropriate.
+- Keep methods and classes focused and concise.
+
+### Commit Messages
+
+- Use clear, descriptive commit messages.
+- Reference issues or pull requests when relevant.
+
+## Code of Conduct
+
+Please be respectful and considerate in all interactions.  
+See [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
+
+## Questions?
+
+Open an issue or contact the maintainer via [LinkedIn](https://www.linkedin.com/in/jens-tirsvad-nielsen-13b795b9/).
+
+---
+Thank you for helping make TirsvadWeb.JwtAuth better!

LICENSE LICENSE.txtLICENSE renamed to LICENSE.txt

@@ -1 +1,87 @@
-# PS.Logging
+[![downloads][downloads-shield]][downloads-url] [![Contributors][contributors-shield]][contributors-url] [![Forks][forks-shield]][forks-url] [![Stargazers][stars-shield]][stars-url] [![Issues][issues-shield]][issues-url] [![License][license-shield]][license-url] [![LinkedIn][linkedin-shield]][linkedin-url]
+
+# ![Logo][Logo] Logging
+PowerShell Logging Module
+
+## Overview
+PS.Logging is a PowerShell module designed to facilitate logging in PowerShell scripts and modules.
+It provides a simple and flexible way to log messages with different severity levels, making it easier to track and debug script execution.
+
+## Features
+- Supports multiple log levels (e.g., Info, Warning, Error)
+- Easy integration with existing PowerShell scripts
+- Lightweight and fast
+
+## Quick Start
+
+### Download and Install
+To install the PS.Logging module, you can use the following PowerShell command:
+```powershell
+Install-Module -Name PS.Logging -Scope CurrentUser
+```
+#### Import the Module
+After installation, import the module into your PowerShell session:
+```powershell
+Import-Module PS.Logging
+```
+#### Basic Usage
+You can start logging messages using the `Write-Log` cmdlet. Here are some examples:
+```powershell
+Write-Header -Message "How to use Logging Examples"
+# Log an informational message
+Write-Info -Message "This is an informational message."
+# Log a warning message
+Write-Warn -Message "This is a warning message."
+# Log an error message
+Write-Err -Message "This is an error message."
+```
+
+### Git Repository
+You can clone the repository using the following command:
+```powershell
+git clone https://github.com/TirsvadScript/PS.Logging.git
+```
+
+## Testing
+The module includes a suite of Pester tests to ensure functionality and reliability. To run the tests, use the following command:
+```powershell
+try { powershell -NoProfile -NoLogo -Command "Import-Module Pester -ErrorAction SilentlyContinue; Invoke-Pester -Script .\logging.Tests.ps1 -OutputFormat NUnitXml -OutputFile test-results.xml" } finally { if ($?) { echo "bbb6c4dc03844c2986fd1ddfd0ceb545=$?" } else { echo "bbb6c4dc03844c2986fd1ddfd0ceb545=$?" } }
+```
+
+## Contributing
+Contributions are welcome. Please follow the guidelines in `CONTRIBUTING.md` and open issues or pull requests.
+
+See [CONTRIBUTING.md](CONTRIBUTING.md)
+
+## Reporting Bugs
+1. Go to the Issues page: [GitHub Issues][githubIssue-url]
+2. Click "New Issue" and provide steps to reproduce, expected behavior, actual behavior, environment, and attachments (logs/screenshots).
+
+## License
+Distributed under the AGPL-3.0 License. See [LICENSE.txt](LICENSE.txt) or [license link][license-url].
+
+## Contact
+Jens Tirsvad Nielsen - [LinkedIn][linkedin-url]
+
+## Acknowledgments
+Thanks to contributors and the open-source community.
+
+<!-- MARKDOWN LINKS & IMAGES -->
+[contributors-shield]: https://img.shields.io/github/contributors/TirsvadScript/PS.Logging?style=for-the-badge
+[contributors-url]: https://github.com/TirsvadScript/PS.Logging/graphs/contributors
+[forks-shield]: https://img.shields.io/github/forks/TirsvadScript/PS.Logging?style=for-the-badge
+[forks-url]: https://github.com/TirsvadScript/PS.Logging/network/members
+[stars-shield]: https://img.shields.io/github/stars/TirsvadScript/PS.Logging?style=for-the-badge
+[stars-url]: https://github.com/TirsvadScript/PS.Logging/stargazers
+[issues-shield]: https://img.shields.io/github/issues/TirsvadScript/PS.Logging?style=for-the-badge
+[issues-url]: https://github.com/TirsvadScript/PS.Logging/issues
+[license-shield]: https://img.shields.io/github/license/TirsvadScript/PS.Logging?style=for-the-badge
+[license-url]: https://github.com/TirsvadScript/PS.Logging/blob/master/LICENSE.txt
+[linkedin-shield]: https://img.shields.io/badge/-LinkedIn-black.svg?style=for-the-badge&logo=linkedin&colorB=555
+[linkedin-url]: https://www.linkedin.com/in/jens-tirsvad-nielsen-13b795b9/
+[githubIssue-url]: https://github.com/TirsvadScript/PS.Logging/issues/
+[logo]: https://raw.githubusercontent.com/TirsvadScript/PS.Logging/main/images/logo/32x32/logo.png
+
+
+[downloads-shield]: https://img.shields.io/github/downloads/TirsvadScript/PS.Logging/total?style=for-the-badge
+[downloads-url]: https://github.com/TirsvadScript/PS.Logging/releases

README.md

@@ -0,0 +1,54 @@
+# Security Policy
+
+## Supported Versions
+
+This project is a collection of PowerShell scripts.
+We aim to support the latest PowerShell7.x and Windows PowerShell5.1 runtimes.
+Security fixes will be applied to the `main` branch and released as soon as practical.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.0.x   | :white_check_mark: |
+| 0.1.x   | :x:                |
+
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please report it privately so we can investigate and fix it before public disclosure.
+
+Preferred reporting methods:
+
+- Use GitHub's Security Advisories for this repository (recommended) so the maintainers can coordinate a fix and private disclosure. See: https://docs.github.com/en/code-security/security-advisories
+- If GitHub Security Advisories are not available for you, open a private communication to the repository maintainers (for example an email to the project maintainer) if such contact is published in the repository. Do not post security-sensitive information in public issues or PRs.
+
+If you must use a public channel initially, avoid including exploit code or detailed reproduction steps until a private channel is established.
+
+## What to Include in a Report
+
+Please include as much of the following as possible:
+
+- A clear description of the vulnerability and its impact (confidentiality, integrity, availability).
+- Step-by-step reproduction steps or a minimal proof-of-concept (in a private channel only).
+- Affected versions/files and the environment where the issue was observed (PowerShell version, OS).
+- Any relevant logs, stack traces or configuration snippets.
+- Contact information so the maintainers can follow up.
+
+## Response Process and Timeline
+
+- Acknowledgement: We will acknowledge receipt as soon as practicable.
+- Triage: We will triage and begin an investigation as soon as practicable.
+- Fix: We will work to provide a fix or mitigation as soon as practicable; timelines vary by severity and complexity.
+- Public disclosure: The project follows coordinated disclosure practices. We will coordinate any public disclosure with the reporter; if no agreement is reached, we may disclose after a reasonable period once a fix is available.
+
+## Disclosure Policy
+
+We prefer coordinated disclosure so that users can update safely.
+Please do not publicly disclose vulnerabilities until a maintainer has had a reasonable opportunity to respond and a fix is available.
+
+## Credits
+
+We appreciate security reports and will credit reporters in release notes or acknowledgements unless the reporter requests to remain anonymous.
+
+---
+
+If you have questions about this policy or need an alternate contact method, open an issue marked with the `security` label (avoid posting exploit details) or check the repository README for maintainer contact information.