Skip to content

Repository navigation

Security: hyein-cbio/pi-opencode-mode

Security

Report a vulnerability

SECURITY.md

Security policy

Supported versions

Security fixes target the latest released version, currently 0.2.0. See CHANGELOG.md for the changes and release history.

Host dependency security

Use an up-to-date, matching Pi/TUI pair within the supported range. The default source-checkout development/test lockfile selects 1.5.0; the 0.99.0 / 1.3.0 / 1.4.0 matrix is retained only for compatibility testing. Passing an older SDK's functional tests is not an endorsement of its dependency security.

Pi peers are not bundled in this extension's tarball, but a vulnerable Pi host can still affect an actual installation. Update the host independently; the broad peer range describes API compatibility, not a security-support promise for every older host. Audit the full default tree after npm ci, not only the non-peer subset. Audit results cover known advisories, not all security risks.

Reporting a vulnerability

Do not disclose vulnerabilities, credentials, or private tool results in a public issue or pull request.

Use GitHub's private vulnerability reporting form:

https://github.com/hyein-cbio/pi-opencode-mode/security/advisories/new

If the form is unavailable, open an issue asking only for a private reporting channel, with no technical details or sensitive data. Wait for the maintainer to arrange private contact before sending your report.

Include the affected commit/version, Node and Pi versions, a minimal reproducer using safe mock tools, expected/actual behavior, and likely impact. Do not test against other people's systems or include real secrets. Response times are best-effort; this project has no guaranteed security-response SLA.

Trust boundary

  • Installing this extension executes trusted extension code in Pi's host process.
  • Guest programs can invoke the tools already callable in their session, through Pi's validation and permission/result hooks. Review the tools you enable.
  • The OpenCode interpreter is not an OS sandbox or memory-isolation boundary. Preflight limits only check compatibility; they do not choose tools or authorize calls.
  • Cancellation is cooperative, and cannot undo completed side effects. A host tool that never settles can prevent result delivery beyond the nominal deadline.
  • Text-output limits do not bound host allocations, the complete transcript, or diagnostic/audit metadata outside the documented budgets.

See the README execution contract for exact limits.

There aren't any published security advisories