pi-media-transcribe
Local-first transcription to structured Markdown notes: transcribe YouTube, podcasts and meetings offline with Whisper or Qwen3-ASR, then optionally have an LLM proofread, segment, summarize and file into any notes folder or Obsidian vault.
This report shows the evidence for pi-media-transcribe@0.2.4. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe helper can automatically send saved OpenAI or OpenRouter credentials to the unrelated default DeepSeek endpoint when no explicit key or endpoint is set. This is credential exfiltration in the user-invoked polished workflow.
Decision evidence
public snapshot- The LLM fallback reads saved credentials for DeepSeek, OpenAI, or OpenRouter from ~/.pi/agent/auth.json and returns the first available key without retaining which provider it came from.
- When no endpoint is configured, the helper defaults to https://api.deepseek.com, regardless of which provider supplied the saved key.
- The helper sends the selected key as a Bearer token to the configured endpoint's /v1/chat/completions API.
- The default polished-note path passes the transcript to this helper; the skill directs users to use polished mode for readable notes or summaries.
- The LLM request runs as part of the user-invoked polished transcription workflow, and the package describes the LLM step.
- Users can set LLM_BASE_URL or a configured baseUrl to select an endpoint; --raw skips the LLM call.
Source & flagged code
6 flaggedThe LLM fallback reads saved credentials for DeepSeek, OpenAI, or OpenRouter from ~/.pi/agent/auth.json and returns the first available key without retaining which provider it came from.
skills/media-transcribe/scripts/llm_to_obsidian.pyView on unpkg · L251When no endpoint is configured, the helper defaults to https://api.deepseek.com, regardless of which provider supplied the saved key.
skills/media-transcribe/scripts/llm_to_obsidian.pyView on unpkg · L233Findings
Affected versions and remediation
This report applies to pi-media-transcribe@0.2.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing pi-media-transcribe@0.2.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.