Skip to content

Dependency hygiene: clear audit findings in Charter workspace #226

@stackbilt-admin

Description

@stackbilt-admin

Summary

Charter's own workspace needs a dependency hygiene pass. This came up while consuming @stackbilt/[email protected] from img-forge: the published CLI is current, but Charter's repo audit still reports vulnerable transitive packages in the MCP SDK and Vitest/Vite tooling paths.

Evidence from live repo check

From /mnt/c/users/kover/documents/charter on main:

Candidate remediation tested locally

A focused root pnpm.overrides block plus explicit root [email protected] reduced the audit to zero known vulnerabilities:

"devDependencies": {
  "vite": "7.3.2"
},
"pnpm": {
  "overrides": {
    "@hono/node-server": "1.19.14",
    "esbuild": "0.28.1",
    "fast-uri": "4.0.0",
    "hono": "4.12.25",
    "ip-address": "10.1.1",
    "qs": "6.15.2",
    "vite": "7.3.2"
  }
}

After this, pnpm audit --audit-level moderate returned:

No known vulnerabilities found

And dependency paths resolved to patched versions:

Additional test gap surfaced

The full test suite has an unrelated stale assertion:

packages/scaffold-core/src/__tests__/package.test.ts
expected '1.2.0' to be '1.1.0'

packages/scaffold-core/package.json reports 1.2.0, so the test should be updated or made less brittle as part of this cleanup.

Acceptance criteria

  • Apply the dependency hygiene change in Charter's root package.json / pnpm-lock.yaml.
  • Confirm pnpm audit --audit-level moderate reports no known vulnerabilities.
  • Fix the stale scaffold-core version assertion.
  • Run Charter's normal package validation:
    • pnpm run build
    • pnpm run typecheck
    • pnpm run test
    • pnpm run publish:check
    • pnpm run verify:adf

Notes

Avoid broad major upgrades for this pass. typescript@6 and zod@4 showed as latest, but they are breaking-major candidates and are not needed for the audit cleanup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions