Skip to content

Security: PidgeonHealth/docs

Security

Report a vulnerability

SECURITY.md

Security Policy

The Pidgeon Health team takes security seriously. This document explains how to report a suspected vulnerability and what to expect when you do.

Reporting a vulnerability

Do not open a public issue for security reports. Public issues let attackers learn about the vulnerability before it is fixed.

Two private channels:

  1. Preferred — GitHub Security Advisory. Open a private advisory from this repository's Security → Advisories tab. This creates an encrypted, audited channel and lets us collaborate on a fix without early disclosure.
  2. Email.security@pidgeon.health. Encrypt with our PGP key (see the published PGP key) if you can; unencrypted reports are also accepted.

Please include:

  • A description of the vulnerability and its impact.
  • Steps to reproduce (proof-of-concept, exact request, or a sample message that triggers it).
  • The component affected (CLI, engine, MCP server, or a desktop app), the version or commit, and the OS/runtime if relevant.
  • Whether the vulnerability is already public elsewhere (CVE, blog post, social, etc.).

Scope

In scope:

  • The code in this repository.
  • Data handling: how the software transmits, stores, or logs information that originates from a user.

Out of scope:

  • Third-party dependencies. Report to the upstream project; we incorporate their fix once available.
  • Issues that require physical access to a user's device.
  • Spam, social engineering, or phishing reports.
  • Self-XSS, CSRF on logout, missing security headers without a demonstrable impact, and other low-impact issues that do not translate into a real attack.

Response

We aim to acknowledge a report within 2 business days, provide an initial assessment (severity, scope, projected fix timeline) within 5 business days, and ship a fix for high-severity issues within 30 days of confirmation (lower-severity within 90 days). Pidgeon is a small team; we will keep you informed if anything slips.

Coordinated disclosure

We follow coordinated disclosure: please give us a reasonable window to ship a fix before publishing details. We are happy to credit reporters in the resulting advisory unless you prefer to stay anonymous. We do not currently run a paid bug bounty program.

Healthcare-data note

Pidgeon's community tools generate synthetic data — they do not process real PHI, and the community engine runs locally with no cloud message-content egress. If your report involves a way for local data to escape a user's machine, treat it as critical and we will too.

There aren't any published security advisories

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Overview · PidgeonHealth/docs · GitHub
Skip to content
Security: PidgeonHealth/docs
Security
Report a vulnerability

SECURITY.md

Security Policy
The Pidgeon Health team takes security seriously. This document explains how to report a
suspected vulnerability and what to expect when you do.
Reporting a vulnerability
Do not open a public issue for security reports. Public issues let attackers learn about
the vulnerability before it is fixed.
Two private channels:
  1. Preferred — GitHub Security Advisory. Open a private advisory from this repository's
Security → Advisories tab. This creates an encrypted, audited channel and lets us
collaborate on a fix without early disclosure.
  2. Email.security@pidgeon.health. Encrypt with our PGP key (see the published PGP
key) if you can; unencrypted reports are
also accepted.
Please include:
  • A description of the vulnerability and its impact.
  • Steps to reproduce (proof-of-concept, exact request, or a sample message that triggers it).
  • The component affected (CLI, engine, MCP server, or a desktop app), the version or commit,
and the OS/runtime if relevant.
  • Whether the vulnerability is already public elsewhere (CVE, blog post, social, etc.).
Scope
In scope:
  • The code in this repository.
  • Data handling: how the software transmits, stores, or logs information that originates from
a user.
Out of scope:
  • Third-party dependencies. Report to the upstream project; we incorporate their fix once
available.
  • Issues that require physical access to a user's device.
  • Spam, social engineering, or phishing reports.
  • Self-XSS, CSRF on logout, missing security headers without a demonstrable impact, and other
low-impact issues that do not translate into a real attack.
Response
We aim to acknowledge a report within 2 business days, provide an initial assessment
(severity, scope, projected fix timeline) within 5 business days, and ship a fix for
high-severity issues within 30 days of confirmation (lower-severity within 90 days).
Pidgeon is a small team; we will keep you informed if anything slips.
Coordinated disclosure
We follow coordinated disclosure: please give us a reasonable window to ship a fix before
publishing details. We are happy to credit reporters in the resulting advisory unless you
prefer to stay anonymous. We do not currently run a paid bug bounty program.
Healthcare-data note
Pidgeon's community tools generate synthetic data — they do not process real PHI, and the
community engine runs locally with no cloud message-content egress. If your report involves a
way for local data to escape a user's machine, treat it as critical and we will too.
 There aren't any published security advisories


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Overview · PidgeonHealth/docs · GitHub
Skip to content
Security: PidgeonHealth/docs
Security
Report a vulnerability

SECURITY.md

Security Policy
The Pidgeon Health team takes security seriously. This document explains how to report a
suspected vulnerability and what to expect when you do.
Reporting a vulnerability
Do not open a public issue for security reports. Public issues let attackers learn about
the vulnerability before it is fixed.
Two private channels:
  1. Preferred — GitHub Security Advisory. Open a private advisory from this repository's
Security → Advisories tab. This creates an encrypted, audited channel and lets us
collaborate on a fix without early disclosure.
  2. Email.security@pidgeon.health. Encrypt with our PGP key (see the published PGP
key) if you can; unencrypted reports are
also accepted.
Please include:
  • A description of the vulnerability and its impact.
  • Steps to reproduce (proof-of-concept, exact request, or a sample message that triggers it).
  • The component affected (CLI, engine, MCP server, or a desktop app), the version or commit,
and the OS/runtime if relevant.
  • Whether the vulnerability is already public elsewhere (CVE, blog post, social, etc.).
Scope
In scope:
  • The code in this repository.
  • Data handling: how the software transmits, stores, or logs information that originates from
a user.
Out of scope:
  • Third-party dependencies. Report to the upstream project; we incorporate their fix once
available.
  • Issues that require physical access to a user's device.
  • Spam, social engineering, or phishing reports.
  • Self-XSS, CSRF on logout, missing security headers without a demonstrable impact, and other
low-impact issues that do not translate into a real attack.
Response
We aim to acknowledge a report within 2 business days, provide an initial assessment
(severity, scope, projected fix timeline) within 5 business days, and ship a fix for
high-severity issues within 30 days of confirmation (lower-severity within 90 days).
Pidgeon is a small team; we will keep you informed if anything slips.
Coordinated disclosure
We follow coordinated disclosure: please give us a reasonable window to ship a fix before
publishing details. We are happy to credit reporters in the resulting advisory unless you
prefer to stay anonymous. We do not currently run a paid bug bounty program.
Healthcare-data note
Pidgeon's community tools generate synthetic data — they do not process real PHI, and the
community engine runs locally with no cloud message-content egress. If your report involves a
way for local data to escape a user's machine, treat it as critical and we will too.
 There aren't any published security advisories


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Overview · PidgeonHealth/docs · GitHub
Skip to content
Security: PidgeonHealth/docs
Security
Report a vulnerability

SECURITY.md

Security Policy
The Pidgeon Health team takes security seriously. This document explains how to report a
suspected vulnerability and what to expect when you do.
Reporting a vulnerability
Do not open a public issue for security reports. Public issues let attackers learn about
the vulnerability before it is fixed.
Two private channels:
  1. Preferred — GitHub Security Advisory. Open a private advisory from this repository's
Security → Advisories tab. This creates an encrypted, audited channel and lets us
collaborate on a fix without early disclosure.
  2. Email.security@pidgeon.health. Encrypt with our PGP key (see the published PGP
key) if you can; unencrypted reports are
also accepted.
Please include:
  • A description of the vulnerability and its impact.
  • Steps to reproduce (proof-of-concept, exact request, or a sample message that triggers it).
  • The component affected (CLI, engine, MCP server, or a desktop app), the version or commit,
and the OS/runtime if relevant.
  • Whether the vulnerability is already public elsewhere (CVE, blog post, social, etc.).
Scope
In scope:
  • The code in this repository.
  • Data handling: how the software transmits, stores, or logs information that originates from
a user.
Out of scope:
  • Third-party dependencies. Report to the upstream project; we incorporate their fix once
available.
  • Issues that require physical access to a user's device.
  • Spam, social engineering, or phishing reports.
  • Self-XSS, CSRF on logout, missing security headers without a demonstrable impact, and other
low-impact issues that do not translate into a real attack.
Response
We aim to acknowledge a report within 2 business days, provide an initial assessment
(severity, scope, projected fix timeline) within 5 business days, and ship a fix for
high-severity issues within 30 days of confirmation (lower-severity within 90 days).
Pidgeon is a small team; we will keep you informed if anything slips.
Coordinated disclosure
We follow coordinated disclosure: please give us a reasonable window to ship a fix before
publishing details. We are happy to credit reporters in the resulting advisory unless you
prefer to stay anonymous. We do not currently run a paid bug bounty program.
Healthcare-data note
Pidgeon's community tools generate synthetic data — they do not process real PHI, and the
community engine runs locally with no cloud message-content egress. If your report involves a
way for local data to escape a user's machine, treat it as critical and we will too.
 There aren't any published security advisories


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
Overview · PidgeonHealth/docs · GitHub
Skip to content
Security: PidgeonHealth/docs
Security
Report a vulnerability

SECURITY.md

Security Policy
The Pidgeon Health team takes security seriously. This document explains how to report a
suspected vulnerability and what to expect when you do.
Reporting a vulnerability
Do not open a public issue for security reports. Public issues let attackers learn about
the vulnerability before it is fixed.
Two private channels:
  1. Preferred — GitHub Security Advisory. Open a private advisory from this repository's
Security → Advisories tab. This creates an encrypted, audited channel and lets us
collaborate on a fix without early disclosure.
  2. Email.security@pidgeon.health. Encrypt with our PGP key (see the published PGP
key) if you can; unencrypted reports are
also accepted.
Please include:
  • A description of the vulnerability and its impact.
  • Steps to reproduce (proof-of-concept, exact request, or a sample message that triggers it).
  • The component affected (CLI, engine, MCP server, or a desktop app), the version or commit,
and the OS/runtime if relevant.
  • Whether the vulnerability is already public elsewhere (CVE, blog post, social, etc.).
Scope
In scope:
  • The code in this repository.
  • Data handling: how the software transmits, stores, or logs information that originates from
a user.
Out of scope:
  • Third-party dependencies. Report to the upstream project; we incorporate their fix once
available.
  • Issues that require physical access to a user's device.
  • Spam, social engineering, or phishing reports.
  • Self-XSS, CSRF on logout, missing security headers without a demonstrable impact, and other
low-impact issues that do not translate into a real attack.
Response
We aim to acknowledge a report within 2 business days, provide an initial assessment
(severity, scope, projected fix timeline) within 5 business days, and ship a fix for
high-severity issues within 30 days of confirmation (lower-severity within 90 days).
Pidgeon is a small team; we will keep you informed if anything slips.
Coordinated disclosure
We follow coordinated disclosure: please give us a reasonable window to ship a fix before
publishing details. We are happy to credit reporters in the resulting advisory unless you
prefer to stay anonymous. We do not currently run a paid bug bounty program.
Healthcare-data note
Pidgeon's community tools generate synthetic data — they do not process real PHI, and the
community engine runs locally with no cloud message-content egress. If your report involves a
way for local data to escape a user's machine, treat it as critical and we will too.
 There aren't any published security advisories


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
Overview · PidgeonHealth/docs · GitHub
Skip to content
Security: PidgeonHealth/docs
Security
Report a vulnerability

SECURITY.md

Security Policy
The Pidgeon Health team takes security seriously. This document explains how to report a
suspected vulnerability and what to expect when you do.
Reporting a vulnerability
Do not open a public issue for security reports. Public issues let attackers learn about
the vulnerability before it is fixed.
Two private channels:
  1. Preferred — GitHub Security Advisory. Open a private advisory from this repository's
Security → Advisories tab. This creates an encrypted, audited channel and lets us
collaborate on a fix without early disclosure.
  2. Email.security@pidgeon.health. Encrypt with our PGP key (see the published PGP
key) if you can; unencrypted reports are
also accepted.
Please include:
  • A description of the vulnerability and its impact.
  • Steps to reproduce (proof-of-concept, exact request, or a sample message that triggers it).
  • The component affected (CLI, engine, MCP server, or a desktop app), the version or commit,
and the OS/runtime if relevant.
  • Whether the vulnerability is already public elsewhere (CVE, blog post, social, etc.).
Scope
In scope:
  • The code in this repository.
  • Data handling: how the software transmits, stores, or logs information that originates from
a user.
Out of scope:
  • Third-party dependencies. Report to the upstream project; we incorporate their fix once
available.
  • Issues that require physical access to a user's device.
  • Spam, social engineering, or phishing reports.
  • Self-XSS, CSRF on logout, missing security headers without a demonstrable impact, and other
low-impact issues that do not translate into a real attack.
Response
We aim to acknowledge a report within 2 business days, provide an initial assessment
(severity, scope, projected fix timeline) within 5 business days, and ship a fix for
high-severity issues within 30 days of confirmation (lower-severity within 90 days).
Pidgeon is a small team; we will keep you informed if anything slips.
Coordinated disclosure
We follow coordinated disclosure: please give us a reasonable window to ship a fix before
publishing details. We are happy to credit reporters in the resulting advisory unless you
prefer to stay anonymous. We do not currently run a paid bug bounty program.
Healthcare-data note
Pidgeon's community tools generate synthetic data — they do not process real PHI, and the
community engine runs locally with no cloud message-content egress. If your report involves a
way for local data to escape a user's machine, treat it as critical and we will too.
 There aren't any published security advisories


, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
})();
Overview · PidgeonHealth/docs · GitHub
Skip to content
Security: PidgeonHealth/docs
Security
Report a vulnerability

SECURITY.md

Security Policy
The Pidgeon Health team takes security seriously. This document explains how to report a
suspected vulnerability and what to expect when you do.
Reporting a vulnerability
Do not open a public issue for security reports. Public issues let attackers learn about
the vulnerability before it is fixed.
Two private channels:
  1. Preferred — GitHub Security Advisory. Open a private advisory from this repository's
Security → Advisories tab. This creates an encrypted, audited channel and lets us
collaborate on a fix without early disclosure.
  2. Email.security@pidgeon.health. Encrypt with our PGP key (see the published PGP
key) if you can; unencrypted reports are
also accepted.
Please include:
  • A description of the vulnerability and its impact.
  • Steps to reproduce (proof-of-concept, exact request, or a sample message that triggers it).
  • The component affected (CLI, engine, MCP server, or a desktop app), the version or commit,
and the OS/runtime if relevant.
  • Whether the vulnerability is already public elsewhere (CVE, blog post, social, etc.).
Scope
In scope:
  • The code in this repository.
  • Data handling: how the software transmits, stores, or logs information that originates from
a user.
Out of scope:
  • Third-party dependencies. Report to the upstream project; we incorporate their fix once
available.
  • Issues that require physical access to a user's device.
  • Spam, social engineering, or phishing reports.
  • Self-XSS, CSRF on logout, missing security headers without a demonstrable impact, and other
low-impact issues that do not translate into a real attack.
Response
We aim to acknowledge a report within 2 business days, provide an initial assessment
(severity, scope, projected fix timeline) within 5 business days, and ship a fix for
high-severity issues within 30 days of confirmation (lower-severity within 90 days).
Pidgeon is a small team; we will keep you informed if anything slips.
Coordinated disclosure
We follow coordinated disclosure: please give us a reasonable window to ship a fix before
publishing details. We are happy to credit reporters in the resulting advisory unless you
prefer to stay anonymous. We do not currently run a paid bug bounty program.
Healthcare-data note
Pidgeon's community tools generate synthetic data — they do not process real PHI, and the
community engine runs locally with no cloud message-content egress. If your report involves a
way for local data to escape a user's machine, treat it as critical and we will too.
 There aren't any published security advisories