Skip to content

SECURITY.md

Latest commit

 

History

History
58 lines (46 loc) · 2.58 KB

SECURITY.md

File metadata and controls

58 lines (46 loc) · 2.58 KB

Security policy

Reporting a vulnerability

Please report security issues privately through GitHub's Private vulnerability reporting form. Do not open a public issue or PR for a suspected vulnerability.

We aim to:

  • Acknowledge the report within 3 business days.
  • Provide an initial assessment (in-scope / out-of-scope, working reproduction, severity estimate) within 7 business days.
  • Coordinate a fix and a disclosure window with the reporter before any public write-up.

Credit will be attributed in the release notes and in the CVE record (if assigned) unless the reporter prefers anonymity.

Supported versions

Only the latest published version on the VS Code Marketplace and Open VSX receives security fixes. Users on older versions should update first; back-ports are considered case-by-case for severe issues.

Threat model

The extension is a thin LSP client that spawns python -m pipeline_check.lsp over stdio. Two categories of issue are in scope:

  1. Code execution from a workspace — the language server is a child process whose command and arguments are configurable. Workspace settings can override these, so a malicious repository could try to coerce arbitrary process spawn at activation time. We mitigate this with VS Code's workspace-trust model (capabilities.untrustedWorkspaces: "limited") and by marking the relevant settings as machine-overridable so workspace overrides require an explicit prompt. Reports demonstrating a bypass are in scope.
  2. Supply-chain integrity of the published .vsix — anything that would let an attacker insert code into a marketplace build (e.g. a leaked publisher PAT, an unpinned tool that ships malicious code, a tag pointing at an off-main commit). Reports about the release workflow are in scope.

Out of scope

  • False-positive or false-negative findings from the upstream pipeline-check rule engine. Report those at dmartinochoa/pipeline-check.
  • Vulnerabilities in dependencies that have a published advisory and an available fix — those are handled by Dependabot and the weekly npm audit CI run, not by ad-hoc reports.
  • Issues that require the user to first install a malicious build of Python or of the pipeline-check package itself. We assume the developer's own toolchain is uncompromised.