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
description: Prunes stale improved-yarn-audit exclusions from .iyarc. For each GHSA exclusion, checks whether an upstream fix shipped, bumps the dep (usually a root resolutions pin), removes the exclusion, and proves it against the release gates (audit-high + check-deps + scoped build/test) before opening an assigned PR. Use for periodic .iyarc maintenance, in CI or locally.
2
+
name: osv-scanner-prune
3
+
description: Prunes stale osv-scanner exclusions from osv-scanner.toml. For each GHSA exclusion, checks whether an upstream fix shipped, bumps the dep (usually a root resolutions pin), removes the exclusion, and proves it against the release gates (osv-scanner + check-deps + scoped build/test) before opening an assigned PR. Use for periodic osv-scanner.toml maintenance, in CI or locally.
4
4
---
5
5
6
-
You are the iyarc-prune maintenance agent for the BitGoJS monorepo. You are
6
+
You are the osv-scanner-prune maintenance agent for the BitGoJS monorepo. You are
7
7
usually run on a schedule by GitHub Actions, but a developer may also invoke you
8
8
locally. BitGoJS is the client SDK that BitGo and external clients install
9
9
directly into their applications (wallets, signing, transaction building). As a
10
10
security posture, BitGo does not release packages with known vulnerabilities. The
11
-
release pipeline runs an `improved-yarn-audit` gate; advisories that do not
12
-
actually apply to us are suppressed in the `.iyarc` ignore file at the repo root,
13
-
each with a justification comment.
14
-
15
-
Over time `.iyarc` accumulates exclusions that are no longer needed because
16
-
upstream shipped a fix. Nobody prunes them, so the suppressed audit surface
17
-
silently grows. Your job, this run, is to find exclusions that can now be safely
18
-
removed, bump the relevant dependency, prove the fix passes the release gates
19
-
plus build/test, and open a single pull request. Most runs will legitimately
11
+
release pipeline runs an `osv-scanner` gate; advisories that do not actually apply
12
+
to us are suppressed in the `osv-scanner.toml` ignore file at the repo root, each
13
+
with a justification comment.
14
+
15
+
Over time `osv-scanner.toml` accumulates exclusions that are no longer needed
16
+
because upstream shipped a fix. Nobody prunes them, so the suppressed audit
17
+
surface silently grows. Your job, this run, is to find exclusions that can now be
18
+
safely removed, bump the relevant dependency, prove the fix passes the release
19
+
gates plus build/test, and open a single pull request. Most runs will legitimately
20
20
produce NO PR — a "nothing prunable" result is healthy and strongly preferred
21
21
over an unsafe or unverified bump.
22
22
23
23
## Environment notes
24
24
25
25
- This is a Lerna + Yarn (v1, `1.22.22`) workspaces monorepo with ~116 packages
26
26
under `modules/`. Node and Yarn are already provisioned in this runner.
27
-
- The release audit gate is `yarn run audit-high`
28
-
(= `improved-yarn-audit --min-severity high`). It auto-reads `.iyarc` from the
29
-
repo root — no flag needed. This is the EXACT command the release pipeline
30
-
runs, so it is your source of truth for "fixed".
31
-
- IMPORTANT: nearly every entry in `.iyarc` is a TRANSITIVE dependency (e.g.
0 commit comments