You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2990205
Browse filesBrowse the repository at this point in the historyBrowse files
Context:
Refresh compatible official tools and locked Python dependencies from v1.2.6.
What changed:
Update Node, OpenCode, Claude Code, OpenSpec, fzf, lazygit, pnpm, Prettier and Wrangler with its owned native graph. Raise the official Debian Chromium security floor on both architectures. Refresh four Python pins, immutable build actions and Trivy. Preserve existing features, data, plugin settings and compatibility holds.
Verification:
132 source tests, workflow pins, Chromium seccomp, JSON/YAML, Compose configurations and Renovate 44.129.0 extraction passed. Generate the Python hash lock under Linux Python 3.13 with official pip-tools 7.6.2; guard against Windows-only graph entries. Independent review covers source, dependency integrity and release documentation. Native image checks remain required before publication.
Release:
Direct main v1.2.7 with v1.2.6 as its sole predecessor. Third-party findings remain accepted upstream vulnerabilities; own-code, secrets, unknown provenance, malformed reports and scanner failures remain blocking. Claude Auth issue #11 stays open without original-path recovery proof.
Copy file name to clipboardExpand all lines: .github/SECURITY.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ If you discover a security vulnerability in HolyCode:
21
21
22
22
HolyCode ships many third-party CLIs inside one Docker image. Tagged releases refresh the pinned Dockerfile tools. The supported Claude Auth plugin is packaged inside the image and installed from that offline payload when enabled. Plugins you install yourself remain outside the image SBOM. Renovate configuration covers images, Actions, npm, PyPI, GitHub releases, and plugin pins; release audits still record scanner findings and compatibility holds before publication.
23
23
24
-
Trivy and Docker Scout keep their full critical/high reports visible. Validated third-party package findings are accepted upstream vulnerabilities and remain listed by dependency, installed version, and vulnerability ID in the release evidence. They do not block delivery. Secret findings, project-owned package findings, unknown package provenance, invalid reports, and scanner failures still block delivery. A passing release does not mean the image has zero vulnerabilities. npm lifecycle scripts are disabled during installation, then checked against exact package versions, integrity values, script bodies, and architecture rules before approved scripts run. Current decisions and owner-guarded replacements are recorded in [`docs/dependency-audit-v1.2.6.md`](../docs/dependency-audit-v1.2.6.md); historical decisions remain in their dated audits.
24
+
Trivy and Docker Scout keep their full critical/high reports visible. Validated third-party package findings are accepted upstream vulnerabilities and remain listed by dependency, installed version, and vulnerability ID in the release evidence. They do not block delivery. Secret findings, project-owned package findings, unknown package provenance, invalid reports, and scanner failures still block delivery. A passing release does not mean the image has zero vulnerabilities. npm lifecycle scripts are disabled during installation, then checked against exact package versions, integrity values, script bodies, and architecture rules before approved scripts run. Current decisions and owner-guarded replacements are recorded in [`docs/dependency-audit-v1.2.7.md`](../docs/dependency-audit-v1.2.7.md); historical decisions remain in their dated audits.
25
25
26
26
When `ENABLE_PAPERCLIP=true`, HolyCode exposes an authenticated local agent board on the configured Paperclip port. Keep that port on trusted LAN/private networks or behind a VPN, and do not publish it directly to the public internet.
0 commit comments