Repository navigation
Conversation
Delete the stale stanzas and reinstall so each range re-resolves to the latest in-range release: - @grpc/grpc-js 1.14.4 -> 1.14.7 (^1.8.10) - brace-expansion 1.1.18 -> 1.1.22 (^1.1.7) - brace-expansion 2.1.4 -> 2.1.8 (^2.0.2) - brace-expansion 5.0.9 -> 5.0.13 (^5.0.8) - source-map-js 1.2.1 -> 1.2.4 (^1.2.1) No package.json changes. picomatch 2.3.2 and 4.0.7 have no fixed release and are left as is. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
|
|
Overall Grade |
Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| JavaScript | Nov 20, 2026 12:35a.m. | Review ↗ |
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
What
Lockfile-only refresh of five HIGH advisories from the DeepSource export.
package.jsonis untouched and there are noresolutions.^1.8.10^1.1.7^2.0.2^5.0.8^1.2.1Fixed advisories: CVE-2026-101915, CVE-2026-101916 (@grpc/grpc-js, fixed in 1.14.5); CVE-2026-102276, CVE-2026-102277, CVE-2026-102278 (brace-expansion, fixed in 1.1.21 / 2.1.7 and later); CVE-2026-93749 (source-map-js, fixed in 1.2.2).
Why
OPS-243. Every parent range already admits the fixed releases, so no parent bump or pin is needed.
How
Deleted the five stale stanzas from
yarn.lockand ranyarn installso each range re-resolved to the latest in-range release (yarn 1yarn upgrade <transitive>is a no-op here). Only those five stanzas moved.Testing
Run with node 24.22.1, yarn 1.22.22.
yarn install --frozen-lockfileon cleannode_modulesgit diff --statyarn.lockonly, 15 insertions, 15 deletionsyarn audit --level highyarn buildyarn lintyarn test(turbo--continue)@steveojs/storage-postgrestestsCan't reach database server)steveocore testsECONNREFUSED)Notes on the local run: the local npm token for
@ordermentum/eslint-config-ordermentum@3.0.1is invalid, so that one package could not be fetched. For install, lint and the frozen-lockfile check only, I temporarily substituted a locally available 4.1.1 build of it and then restored the original stanza, so the committed lockfile has no change to it. Lint therefore ran against 4.1.1 rules, not 3.0.1. Buildkite runs the real install and the service-backed suites.Deferred
^2.3.1) and 4.0.7 (^4.0.4), CVE-2026-112366: no fixed release exists. Not pinned.Dev box
Not applicable: library repo
🤖 Generated with Claude Code