RippleMap v0.6.0 — GitHub Action

RippleMap v0.6.0 — GitHub Action & Cross-Repository Impact Analysis

RippleMap helps engineering teams understand the ripple effects of changes across their repositories.

This release includes a GitHub Action that automatically analyzes pull requests, identifies potentially affected repositories, and posts the results directly in the pull request discussion.

Highlights

GitHub Marketplace Action

• Automatically analyze the potential downstream impact of pull requests.
• Identify directly and indirectly affected repositories.
• Analyze changed files to avoid flagging unrelated dependencies.
• Post and update pull request comments with actionable dependency information.
• Support private repositories through configurable authentication.
• Report incomplete scans and optionally fail CI checks.

Expanded Dependency Detection

• Dockerfiles and Docker Compose
• Terraform modules
• GitHub Actions and reusable workflows
• Kubernetes manifests and Helm charts
• npm, Go, and Python dependencies

Dependency Analysis

• Trace cross-repository dependencies through an interactive graph.
• Detect version drift across shared components.
• Identify unpinned references that may automatically pick up upstream changes.
• Generate self-contained HTML reports that work offline.

Developer Experience

• Scan GitHub organizations without cloning repositories.
• Support Azure DevOps organization scanning.
• Reuse cached repository data to speed up repeat scans.
• Run the CLI on Node.js 22 or newer.

Quick Start

Run RippleMap directly using npm:

npx ripplemap scan --org your-org
npx ripplemap report --open

To integrate RippleMap into your GitHub pull request workflow, follow the setup instructions in the repository README.

Documentation: https://github.com/Zintrivious/ripplemap

Website: https://zintrivious.github.io/ripplemap/

Live Demo: https://zintrivious.github.io/ripplemap/demo/cloudposse/

RippleMap is open source under the MIT license.

ripplemap 0.5.0: pull request comments

ripplemap maps the dependencies between the repos in your org from the files they already contain, so you can see what a change will affect before you merge it.

New: comments on pull requests

# .github/workflows/ripplemap.yml
name: ripplemap
on: pull_request_target
permissions:
  contents: read
  pull-requests: write
jobs:
  impact:
    runs-on: ubuntu-latest
    steps:
      - uses: Zintrivious/ripplemap@v0

The Action comments with the repos a pull request may affect and keeps that comment up to date. Only the part of the repo that changed counts. Repos that pin nothing are flagged as getting the change on merge. It never checks out or runs the pull request's code. See the README for private orgs and inputs. The same analysis runs locally with ripplemap affected.

Also since the first release

• Scan a whole org without cloning: ripplemap scan --org <name>, cached so repeat scans take a few API requests.
• ripplemap report: an interactive, self-contained HTML page with the impact graph and drift.
• More formats: Kubernetes manifests, Helm charts, go.mod, Python (pyproject.toml, requirements.txt), and workflow job containers and services. These join Dockerfiles, Terraform, GitHub Actions, npm and Compose.
• ripplemap unpinned: references to things your repos build that pin no version.
• Never a silent partial graph: anything that couldn't be read is recorded and reported, and --strict fails instead.
• Tested on real orgs: linuxserver, sindresorhus, Cloud Posse, HashiCorp, Argo and Jupyter, with what each turned up fixed.
• Requires Node.js 22 or newer.

Install with npm install -g ripplemap or run with npx ripplemap.