Fix GitHub Security reports

Run the following 2 commands to get security advisiories and dependabot alerts respectively for this repo and create a plan to fix them.

Security advisories

gh api -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" /repos/{owner}/{repo}/security-advisories

Dependabot alerts

gh api -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" /repos/{owner}/{repo}/dependabot/alerts

<system-reminder> Plan mode is active. The user indicated that they do not want you to execute yet -- you MUST NOT make any edits (with the exception of the plan file mentioned below), run any non-readonly tools (including changing configs or making commits), or otherwise make any changes to the system. This supersedes any other instructions you have received.

Plan File Info:

No plan file exists yet. You should create your plan at /home/byk/.local/share/opencode/worktree/51d1015fd1f616acf9a5ffaad9331ec6b304586b/witty-wolf/.opencode/plans/1781024287957-glowing-cabin.md using the write tool. You should build your plan incrementally by writing to or editing this file. NOTE that this is the only file you are allowed to edit - other than this you are only allowed to take READ-ONLY actions.

Plan Workflow

Phase 1: Initial Understanding

Goal: Gain a comprehensive understanding of the user's request by reading through code and asking them questions. Critical: In this phase you should only use the explore subagent type.

1. Focus on understanding the user's request and the code associated with their request

2. Launch up to 3 explore agents IN PARALLEL (single message, multiple tool calls) to efficiently explore the codebase.

• Use 1 agent when the task is isolated to known files, the user provided specific file paths, or you're making a small targeted change.
• Use multiple agents when: the scope is uncertain, multiple areas of the codebase are involved, or you need to understand existing patterns before planning.
• Quality over quantity - 3 agents maximum, but you should try to use the minimum number of agents necessary (usually just 1)
• If using multiple agents: Provide each agent with a specific search focus or area to explore. Example: One agent searches for existing implementations, another explores related components, a third investigates testing patterns

3. ...