Skip to content

Security: philliphoff/EncDotNet.S100

Security

SECURITY.md

Security Policy

We take the security of EncDotNet.S100 seriously. Thank you for helping keep the project and its users safe.

Supported versions

EncDotNet.S100 is pre-1.0 and under active development. Security fixes are applied to the latest released version and shipped in a new release. Please make sure you are running the most recent release before reporting an issue.

Version Supported
Latest release
Older releases

Reporting a vulnerability

Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

Instead, report them privately through GitHub's built-in security advisory workflow:

  1. Go to the Security tab of the repository.
  2. Click "Report a vulnerability" to open a private advisory.
  3. Provide as much detail as you can, including:
    • A description of the vulnerability and its impact.
    • Steps to reproduce, or a proof-of-concept.
    • Affected version(s) and platform(s).
    • Any suggested mitigation, if known.

This channel is private to the maintainers, so details are not disclosed publicly while the issue is being investigated and fixed.

What to expect

  • We will acknowledge your report as soon as we are able to review it.
  • We will investigate, keep you informed of progress, and work on a fix.
  • Once a fix is released, we will publish a security advisory and credit the reporter (unless you prefer to remain anonymous).

Dependencies

This project uses Central Package Management (Directory.Packages.props) and runs gh-advisory-database security checks before introducing new dependencies. If you find a vulnerability that stems from a third-party package, please include the package name and version in your report.

There aren't any published security advisories