Only the latest release gets security fixes. Filee checks for updates, and an installed copy updates in place, so please check that the problem is still there in the latest release before you report it.
Please don't open a public issue for a security problem.
Report it privately with Report a vulnerability on the repository's Security tab.
Include the Filee version, your operating system, what an attacker can do and the steps or file that show it. If a crafted file triggers it, attach the file, or say how to make one.
You'll get a reply as soon as possible. Once the fix is released, the advisory is published and you're credited unless you'd rather not be. A release that fixes a security problem is marked required, so every copy shows it each time it starts until it is updated.
In scope:
- Filee itself: the app, the CLI, Setup, the context menu and Explorer menu, watch folders.
- Files that make Filee do more than convert them, such as writing outside the output folder, running code, or reading files they shouldn't.
- How Filee downloads and checks updates and engines.
Out of scope:
- Bugs in the engines (FFmpeg, LibreOffice, Ghostscript, Pandoc, rhwp, 7-Zip and others). Report those to their projects. Tell us too if Filee should update the pinned version.
- SmartScreen or Gatekeeper warnings: releases up to 2.0.0 aren't code-signed, SmartScreen can still warn about a new signed release for a while, and macOS builds are ad-hoc signed and not notarized (see Code signing policy).
- Attacks that need someone who can already run programs as you on your computer.
- Updates: an installed copy downloads the new installer from GitHub Releases and checks it against the release's
SHA256SUMSfile before it runs it. - Engines: every engine comes from the official location pinned in
engines.json, with its SHA-256 and size. A download that doesn't match is discarded. - Release files: each release lists the SHA-256 of every package in
Filee-<version>-SHA256SUMS.txt.
Filee converts files on your own computer and never uploads them. See the Privacy policy.