Repository navigation
Releases
OpenCode Lookout 0.1.3
OpenCode Lookout 0.1.3
Changed
- Publish through the manual trusted-publishing workflow with OIDC provenance,
the first release after the approved v0.1.2 bootstrap. - Complete npm package metadata: keywords, author, and tests for repository,
homepage, bugs, license, engines, and the packed README/source. Show the npm
version badge and refresh the README install instructions for the published package. - No runtime behavior changes.
Approval and validation
Approved revision 26f1359209807017d5abd85389bee93794c45896 (merge of PR #10). Post-merge CI and full push CodeQL passed on this revision. This is the first release intended for the OIDC trusted-publishing workflow with npm provenance.
npm
Published from the manual Publish npm (manual) workflow after the npm environment approval.
OpenCode Lookout 0.1.2
OpenCode Lookout 0.1.2
Changes
- Add an allowlisted npm package and
lookoutexecutable with independent offline
recovery from a dedicated, stable installation prefix. - Precompile the Solid TUI for installed-package loading; use optional host-provided
SDK/UI peers instead of a duplicate SDK dependency graph. - Audit and test the production-installed package, including exact-tarball Docker
compatibility, cancellation, confirmed controls and recovery. - Add a manually approved trusted-publishing workflow for future npm versions.
- Correct the terminal harness's post-cancellation assertion for changed-cell
redraws without changing runtime behavior or safety checks.
Existing plugin/RPC IDs, /lookout, storage keys, ownership markers and recovery
commands are preserved. v0.1.1 and its signed tag are unchanged.
Approved revision and artifact
The maintainer explicitly approved 753213b51fae8e08f7d2069f4b76bfc131b1cb74
for merge and the signed v0.1.2 GitHub/npm release, conditional on all release gates.
PR #9 records this approval and the first-package bootstrap exception.
- Approved source SHA-256:
23faa5cc0f4f8c410004415359b8b5ff6c44d7b76a513a44168b43daa3092193 - Tested tarball:
opencode-lookout-0.1.2.tgz - SHA-512 integrity:
sha512-NByAWYHvtfZ5BilMUiaN05y64mLQX/P3VEkKHpq3MhRP9Ue0aPJORWkckcItFI8awjUugCTxittSFpdZUJ3rGA==
Validation
43 tests, formatting, documentation, lint, types, generated-source equality,
production-install recovery and consumer audit pass. All configured security
checks pass without findings at any severity. The candidate's full push CodeQL
passes both languages. Docker tests cover the newest five stable OpenCode CLIs,
2.2.2–2.2.6, in wide/default and narrow/tokyonight modes; no next RC was discovered.
Local Linux arm64 and hosted Linux amd64 matrices pass. Node 22/24 runtime checks
and Node 26 quality checks pass. Post-merge CI
42446241891
and full push CodeQL
42446241874
pass on main commit 0a9afff6cf5111eabf6671d312217b901ad9bf33, whose source tree
is identical to the approved candidate.
npm publication and installation
GitHub release publication is separate from npm availability. The approved
first-package bootstrap publishes the exact tested v0.1.2 tarball with the
maintainer's authenticated npm session and private 2FA. This version has no
GitHub OIDC provenance. Future versions will use trusted publishing after
package setup. npm delivery is not complete until registry integrity and a fresh
consumer installation have been verified.
After npm publication, follow the stable-prefix installation instructions.
Direct registry plugin entries and ephemeral npm-exec caches are not owned by the
offline recovery CLI. Use the installed lookout executable for status,
unload, or restore --yes. Before switching from a checkout, restore restrictions
and unload with the old checkout's CLI. No personal installation is migrated.
OpenCode 2.2.2 uses the tested read-only profile; 2.2.3+ supports controls.
The offline CLI supports Node 22+. PTY tests are not pixel-level/accessibility
audits, provider authentication tests, or security guarantees. See
validation
and the threat model.
npm publication record
Published opencode-lookout@0.1.2 on 2026-11-09T02:14:34Z using the approved
first-package bootstrap (maintainer-authenticated, private 2FA). Registry latest
points to 0.1.2, and its SHA-512 integrity matches the tested artifact:
sha512-NByAWYHvtfZ5BilMUiaN05y64mLQX/P3VEkKHpq3MhRP9Ue0aPJORWkckcItFI8awjUugCTxittSFpdZUJ3rGA==
This bootstrap version has no GitHub OIDC provenance. A fresh registry install
passed isolated load, status, unload, and restore --yes checks. The npm
trusted publisher is now configured for repository sodejm/opencode-lookout,
workflow npm-publish.yml, environment npm, so later versions publish with OIDC
provenance through the manual Publish npm (manual) workflow.
OpenCode Lookout 0.1.1
OpenCode Lookout 0.1.1
Corrective GitHub source release. This supersedes v0.1.0, which was returned to draft after its post-merge full CodeQL scan reported a fixture-only finding omitted by PR analysis. The v0.1.0 signed tag is retained unchanged.
Corrections
- Remove an unused temporary dump of the isolated test server's session response. Terminal tests now assert that no response dump is saved.
- Run full CodeQL on candidate branch pushes. Required
Analyzechecks are distinct from change-focusedPR Analyzechecks; a clean PR scan cannot substitute for full-candidate assurance. - Require post-merge full checks and an identical approved source tree before publication. No finding suppression or severity waiver was added.
- Runtime plugin behavior and production dependencies are unchanged from v0.1.0.
Features and compatibility
Lookout provides searchable resource inventory, details and pins, file-sourced plugin descriptions, confirmed exact-ID local controls, and independent offline recovery. Status styling uses native semantic colors; MCP browsing remains native to OpenCode.
The breaking rename uses opencode-lookout, /lookout, bin/lookout.mjs, and lookout: ownership markers, without legacy aliases. Before replacing an older installation, use its own recovery CLI to inspect and restore its owned restrictions and unload it. Do not run both copies. The new CLI does not remove old ownership blocks. See the README and changelog.
- OpenCode 2.2.1–2.2.2: verified read-only inventory, rejected mutations, offline lifecycle, and both terminal browsing modes.
- OpenCode 2.2.3–2.2.5: verified effective skill/MCP/plugin restrictions, recovery, and both terminal modes.
- All ten cases pass on local Linux arm64 and hosted Linux amd64. No next-release RC was available during discovery.
- Development requires Node 26.4.0+ and npm 11+. The production-only offline CLI retains Node 22+ support; hosted runtime checks use npm 11.19.1 and Node 22/24.
Validation and approval
Approved/tagged revision: e5e19a93daa635c04df252f9cb3f6acace6b786c.
Source SHA-256: d4cab949320a754741f22b3fe8013265cfc7c6ce222b8064483a3c9e93c5798b.
- All 37 tests, formatting, docs, lint, and type checks pass.
- npm audit/signatures, Semgrep, full-history/current-source Gitleaks, Trivy, and full CodeQL pass without configured findings or errors.
- Candidate CI and full push-event CodeQL pass. Exact-revision maintainer approval is recorded in PR #7.
- Before publication, all eight full post-merge checks passed on
2dd58c9d34069f419f77ff24a7e980f0df783ffb: main CI, main CodeQL. Its source tree matches the approved tagged candidate exactly. No open CodeQL or Dependabot alerts remained at publication.
Limits
Clean configured scans are not a security guarantee. Terminal tests are not pixel-level or accessibility audits; provider authentication, quota, remote-server behavior, and other terminal sizes are not certified. Controls affect global configuration and do not revoke content already loaded into conversations.
This is a GitHub source release, not an npm publication. private: true remains enabled. No personal configuration, credentials, raw logs, or retained fixtures are attached. MIT licensed; not an official OpenCode product.