Skip to content

fix(ci): resolve npm audit findings - #23

Merged
erwinmsmith merged 1 commit into
mainfrom
fix/ci-resolve-audit-findings
Aug 14, 2026
Merged

fix(ci): resolve npm audit findings#23
erwinmsmith merged 1 commit into
mainfrom
fix/ci-resolve-audit-findings

Conversation

@erwinmsmith

Copy link
Copy Markdown
Contributor

Problem

The Repository gates CI job runs npm audit and has been failing on every recent main build with 2 high-severity findings:

  • js-yaml 3.15.0 / 4.3.0 — quadratic CPU consumption in !!omap resolution (CVE-2026-59870)
  • nanoid 3.3.16 — custom generators can loop indefinitely when size is zero

Change

npm audit fix bumps only the lockfile entries:

  • js-yaml 3.15.0 → 3.15.1, 4.3.0 → 4.3.1
  • nanoid 3.3.16 → 3.3.18

No package.json ranges changed.

Verification

  • npm audit → 0 vulnerabilities ✅
  • npm run build:packages
  • npx vitest run packages/skills/src/skills.test.ts (12 tests) ✅

The Repository gates job runs npm audit and currently fails on every
recent main build:

- js-yaml 3.15.0 / 4.3.0: quadratic CPU consumption in !!omap resolution
  (CVE-2026-59870)
- nanoid 3.3.16: custom generators can loop indefinitely when size is zero

npm audit fix upgrades the transitive lockfile entries to js-yaml
3.15.1/4.3.1 and nanoid 3.3.18. Build and package tests still pass.
@erwinmsmith
erwinmsmith merged commit 053bd9a into main Aug 14, 2026
4 checks passed
@erwinmsmith
erwinmsmith deleted the fix/ci-resolve-audit-findings branch August 14, 2026 04:08
erwinmsmith added a commit that referenced this pull request Aug 14, 2026
The published 1.0.0 line predates two fixes now on main:

- #22 ships the framework built-in skills inside @codesoul-co/hypha-skills
  (tarball data + resolveBuiltinSkillsDirectory export);
- #23 resolves the npm audit findings that fail the Repository gates job.

The patch release moves the whole release line to 1.0.1 with exact-version
internal dependencies.
erwinmsmith added a commit to erwinmsmith/THETA-Agent that referenced this pull request Aug 14, 2026
Hypha is no longer a local third_party checkout. THETA-Agent now depends
on the published @codesoul-co/hypha-* npm release line (1.0.1) exactly as
Hypha's official release guidance prescribes; THETA remains the single
third_party upstream checkout.

- manifests: replace all file:third_party/Hypha dependencies with
  @codesoul-co/hypha-*@1.0.1 and drop the hypha:install/hypha:build steps
- imports: rename every @hypha/* import across agent, tools, domain to the
  published package names
- skills: load Hypha built-in skills from the shipped
  resolveBuiltinSkillsDirectory() data of @codesoul-co/hypha-skills instead
  of a source checkout
- doctor: replace hypha.lock/hypha.build checks with hypha.packages, which
  verifies the installed release line, package entries, and shipped built-ins
- upstreams: config/upstreams.lock.json now pins only THETA
- tooling: allow better-sqlite3 postinstall for pnpm; update repository
  validation, README, architecture and CLI docs accordingly

Hypha-side fixes released upstream and consumed here:
- CodeSoul-co/Hypha#22 ships built-in skills in the hypha-skills tarball
- CodeSoul-co/Hypha#23 resolves the npm audit failures
- CodeSoul-co/Hypha#24 prepares and publishes @codesoul-co/hypha-* 1.0.1
- CodeSoul-co/Hypha#25 makes the official consumer example compile from
  the registry

Verified: build, test:registries, test:providers, test:docs, test:python,
validate, doctor, governed demo, REPL, and the HTTP API all pass without a
Hypha checkout.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant