RippleLab

Mapping the blast radius

Generated narrative

Analysis report

Executive summary

This dependency ecosystem contains 30 packages serving 6 applications through 68 dependency relationships. Analysis identified 2 critical chokepoints with Ripple Scores above 0.70. The most critical package is express (Ripple Score: 1.00), which sits on the dependency path of 6 of 6 applications. A single compromise of express would expose 21% of the ecosystem across 1 propagation levels.

Critical dependencies ranking

#PackageRipple ScoreTypeApps affectedRecommended action
1express
1.00
Library6/6Replace or vendor-pin immediately
2winston
0.87
Library6/6Replace or vendor-pin immediately
3lodash
0.57
Foundational6/6Pin version + monitor advisories
4debug
0.51
Foundational6/6Pin version + monitor advisories
5mongoose
0.49
Library3/6Pin version + monitor advisories

Risk heat map

Propagation depth from each package to each application. Red = direct or near-direct (≤2 hops), amber = indirect, green = not on the path.

Packageauth-servicepayment-gatewayuser-dashboardapi-gatewaynotification-serviceanalytics-engine
express
1
1
1
1
1
1
axios
—
—
1
1
—
1
jsonwebtoken
1
—
—
—
—
—
mongoose
1
1
—
—
—
1
bcrypt
1
—
—
—
—
—
cors
1
—
1
1
—
—
helmet
1
1
—
1
—
—
winston
1
1
1
1
1
1
joi
—
1
—
1
—
—
ioredis
—
—
1
—
1
1
socket.io
—
—
1
—
—
—
bull
—
—
—
—
1
—
nodemailer
—
—
—
—
1
—
stripe
—
1
—
—
—
—
lodash
2
2
2
2
2
2
debug
2
2
2
2
2
2
ms
2
2
2
—
2
2
semver
2
2
—
2
2
2
colors
2
2
2
2
2
2
minimist
—
—
—
—
—
—
qs
2
2
2
2
2
2
safer-buffer
2
2
2
2
2
2
inherits
2
2
2
2
2
2
depd
2
2
2
2
2
2

Propagation analysis

express v4.18.2 — Ripple Score 1.00

express (v4.18.2) is a library package with a Ripple Score of 1.00. It is a direct dependency of 6 packages (auth-service, payment-gateway, user-dashboard, api-gateway, notification-service, analytics-engine), giving it a relative degree centrality of 1.00. Through those intermediaries it reaches 6 of 6 end-user applications (100% downstream reach). Its relative betweenness centrality of 1.00 means it sits on a large share of the shortest propagation paths between the foundational and application layers. A compromise here would contaminate 6 packages within 1 hop.

winston v3.10.0 — Ripple Score 0.87

winston (v3.10.0) is a library package with a Ripple Score of 0.87. It is a direct dependency of 6 packages (auth-service, payment-gateway, user-dashboard, api-gateway, notification-service, analytics-engine), giving it a relative degree centrality of 0.90. Through those intermediaries it reaches 6 of 6 end-user applications (100% downstream reach). Its relative betweenness centrality of 0.75 means it sits on a large share of the shortest propagation paths between the foundational and application layers. A compromise here would contaminate 6 packages within 1 hop.

lodash v4.17.21 — Ripple Score 0.57

lodash (v4.17.21) is a foundational package with a Ripple Score of 0.57. It is a direct dependency of 9 packages (axios, jsonwebtoken, mongoose, joi, ioredis, bull, nodemailer, stripe, cors), giving it a relative degree centrality of 0.90. Through those intermediaries it reaches 6 of 6 end-user applications (100% downstream reach). Its relative betweenness centrality of 0.00 means it sits on a large share of the shortest propagation paths between the foundational and application layers. A compromise here would contaminate 15 packages within 2 hops.

Mitigation priorities

  1. 1Establish vendor and advisory monitoring for express, winston, lodash — these carry the highest Ripple Scores in the graph.
  2. 2Evaluate audited alternatives for every package scoring above 0.70 (2 today), starting with express → fastify.
  3. 3Implement strict dependency pinning and lockfile integrity checks for all foundational packages.
  4. 4Add runtime integrity verification (Sigstore / provenance attestation) for packages on the critical propagation paths.
  5. 5Rehearse the isolation playbook quarterly so containment does not orphan production services unexpectedly.