# Security policy

## Reporting a vulnerability

Do not open a public GitHub issue for a security report.

Use GitHub private vulnerability reporting on this repository (Security tab,
"Report a vulnerability"). If that form is unavailable, email the maintainer
through the GitHub profile listed on the repo.

You should hear an acknowledgment within 48 hours and a status update within
7 days. Coordinated disclosure follows a fix, or 90 days, whichever is sooner.

## Supported versions

Only the latest published 0.x release is supported until a 1.0 line exists.

## What this plugin can reach

dsh plugins run with the user's permissions, unsandboxed, inside the dsh
profile. MedSeek in particular:

- Registers eight tools on the global tool registry.
- Makes HTTPS requests only to the hosts listed in `docs/permissions-and-data.md`
  (NLM, NIH, FDA). Those requests carry search terms and codes, never a
  session log.
- Writes nothing of its own to disk. dsh itself appends tool arguments and
  results to the session jsonl log; that log is not encrypted by this plugin.
- Does not phone home, does not ship telemetry, and does not load remote
  scripts.

## Health data

The plugin does not require protected health information to function. Local
tools accept pasted text; lookup tools send terms and codes to public APIs.
Anyone deploying against real patient data is responsible for their own
HIPAA / GDPR posture, including:

- running dsh on infrastructure they control
- keeping `DSH_TELEMETRY_MODE` unset or `DISABLED`
- pointing session storage at an encrypted volume
- using a model provider covered by their BAA, or local weights
- treating the session directory as PHI storage

This is a scope clarification, not legal advice.

## Dependencies

The lockfile is committed. `pnpm audit` runs in CI.