Add node-provider-proxy CI gate failing on high/critical npm audit findings - #8
Merged
Merged
Conversation
…ndings Security team requirement: dependency audits at the high level must pass in CI. Audits both the repo-root lockfile (shared workspace libraries under c3-api/lib, which the proxy declares as workspaces) and node-provider-proxy's own lockfile. Triggers include c3-api/lib/** since the proxy builds against those shared libraries. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
coburncoburn
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the security team's required dependency-audit gate for node-provider-proxy: CI fails on any high or critical
npm auditadvisory. (Sibling PR #7 adds the same gate for c3-api.)c3-api/lib/*, which the proxy declares as its own workspaces —fallible,json-rpc,well-known-*) and node-provider-proxy itself.npm audit --audit-level=highis the whole gate — npm's exit code respects the level flag, so no wrapper script is needed, and no install step is required.node-provider-proxy/**,c3-api/lib/**(shared libs the proxy builds against), the root lockfile, and the workflow itself.workflow_dispatchallows manual re-runs when new advisories publish without a code change.No dependency changes: both lockfiles currently pass (node-provider-proxy has 7 low remaining, below the gate).
Test plan
npm audit --audit-level=highexits 0 locally in both the repo root andnode-provider-proxy/workflow_dispatch(path filters mean this PR itself won't run it) and confirm it passes🤖 Generated with Claude Code