Skip to content

CI blocked by picomatch high advisory GHSA-fc5q-39xc-vjpf through knip #317

Closed

Description

@arminazimi

CI failure

PR #316 was rerun after its first CI attempt was cancelled. In attempt 2, Windows Node 24 and both Linux shards on Node 22 passed. Linux Node 24 shard 1 passed as well.

Linux Node 24 shard 0 passed its tests, browser forecast test, quality ratchet, mutation ratchet, and production-only npm audit. Its all-dependency audit then rejected the high advisory GHSA-fc5q-39xc-vjpf affecting picomatch <=4.0.7.

Current dependency path

npm ls picomatch shows knip@6.44.1 -> picomatch@4.0.7 and knip -> tinyglobby -> picomatch.

npm view picomatch version returned 4.0.7 on November 17, 2026. The reviewed advisory currently lists no patched version. The local npm audit --json reproduces the same advisory. The dependency was already in the base lockfile.

Completion

Use a published, compatible fix once available, or a verified replacement for the affected development dependency. Re-run npm audit, the dead-code check, npm run check, and the full PR CI.

The repository quality policy rejects high-severity advisories. Its threshold and allowlist should retain their current behavior.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions