Skip to content

Security: Jeffrey-Tool-Projects/FileTree

Security

SECURITY.md

Security policy

Supported versions

Security fixes are provided for the latest release and the default branch. Older releases are not supported. Upgrade before reporting an issue that may already be fixed.

Reporting a vulnerability

Do not open a public issue, pull request, or discussion for a suspected vulnerability.

Use either private channel:

  • GitHub Security Advisories. Open a private report from this repository's Security tab, Report a vulnerability. This is the preferred channel.
  • Email. jechenmailman@gmail.com, with a subject line that begins with [SECURITY].

Include the affected version, platform, impact, and steps to reproduce. Do not attach credentials, tokens, or unredacted logs.

The maintainers aim to acknowledge a report within 5 business days, and to coordinate a fix and disclosure within 90 days. There is no bug-bounty promise.

Operational notes

FileTree reads metadata for paths the operator selects. Process launches do not use a shell.

Do not run virtual-disk compaction on an extended-length path (the Win32 prefix written as backslash-backslash-question-backslash), a UNC path, or a Volume path until that path is pinned inside the chosen directory. A path of that form can currently be resolved relative to the working directory.

There aren't any published security advisories