jetbrains-fish is a JetBrains IDE plugin that adds fish shell syntax highlighting, fish-lsp code intelligence and fish run configurations. This policy says how to report a security problem and how we decide whether a report is one.

Do not open a public issue for a security problem. Use GitHub's private vulnerability reporting. If neither works for you, email gaborjbernat@gmail.com.

Include what the attacker controls and what they gain, the steps or a proof of concept, and the versions and platform you tested. Write the report yourself; unreviewed tool or model output takes longer to triage.

Volunteers maintain jetbrains-fish, with no on-call rotation. We aim to acknowledge a report within 5 working days and assess it within 15 working days. Fixes are developed in a private fork attached to the draft advisory, ship in a new release, and the advisory, with a CVE requested through GitHub, goes out with that release. The default embargo is 90 days from the report; we agree any change with the reporter. We credit reporters in the advisory under the name they choose, or not at all. There is no bug bounty.

Only the latest release receives fixes. Confirm the problem reproduces on it before reporting.

A report is a vulnerability when an attacker who controls only an input that the threat model lists as untrusted breaks a guarantee jetbrains-fish makes. A report that first needs control of something the threat model trusts, such as the IDE, a run configuration you start, or the fish and fish-lsp binaries, is a bug: we fix it in the open and publish no advisory. Classify by who supplies the dangerous input, not by how bad the outcome sounds.

In scope

• The plugin executing a fish script without the user starting a run configuration.
• Run configuration fields (script path, arguments) reaching a shell as code rather than as separate arguments.
• Highlighting or parsing a file causing the plugin, not fish-lsp, to run a program or touch other files.

Out of scope

• Running a script: a run configuration executes the script it names, with the user's rights.
• What fish-lsp does with the files it is given; report that to fish-lsp.
• Vulnerabilities in fish; see the fish security policy.
• Vulnerabilities in the IntelliJ Platform or LSP4IJ.

If you cannot tell which side a finding falls on, report it privately and we will decide.