Analysis updated 2026-07-08 · repo last pushed 2026-07-07
Detect when a contributor changes the Node version your project supports and trigger compatibility tests across multiple versions.
Flag pull requests that modify dependencies so reviewers can give them extra attention before merging.
Automatically post a comment on pull requests that change sensitive package.json fields like engines or scripts.
| joshuakgoldberg/package-change-detector-action | arashthr/hugo-flow | argeneau12e/kairos-tx | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | TypeScript | TypeScript | TypeScript |
| Last pushed | 2026-07-07 | — | — |
| Maintenance | Active | — | — |
| Setup difficulty | easy | moderate | hard |
| Complexity | 2/5 | 3/5 | 4/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Just add the action to an existing GitHub Actions workflow on pull requests and specify which package.json properties to watch.
Package Change Detector Action is a small tool for teams who use GitHub to manage their code. It watches pull requests and tells you whether someone modified specific parts of a project's package.json file, the file that describes a JavaScript project's dependencies, required tools, and other metadata. Instead of manually checking whether a contributor bumped a Node version requirement or changed a dependency, you can plug this action into your workflow and get a simple yes-or-no answer automatically. At a high level, you add this action to a GitHub workflow that runs on pull requests. You tell it which properties in package.json you care about, for example, engines, which specifies which versions of Node or npm your project requires. When a pull request comes in, the action compares the relevant bits of the file and sets an output variable called changed to true or false. Your workflow can then use that answer to trigger other steps, like running extra tests, posting a comment, or flagging the change for review. The people who'd reach for this are typically maintainers of open-source projects or engineering teams with established CI pipelines. Say you maintain a popular library and contributors regularly submit pull requests. If someone changes the Node version your package supports, you might want to run compatibility tests across multiple Node versions before merging. This action lets your workflow detect that change and act on it without anyone having to remember to check manually. The README is fairly sparse and doesn't go into much detail beyond the basic usage example. It's written in TypeScript with strict type checking, which suggests the author cares about correctness, but there's little documentation about edge cases, supported property formats, or advanced configuration. The project appears to be early-stage given its low adoption, so if your needs go beyond simple property detection, you may find yourself reading the source to understand what's possible.
A GitHub Action that checks whether a pull request changed specific fields in your project's package.json file, like Node version requirements or dependencies, and gives you a yes-or-no answer you can use to trigger other workflow steps.
Mainly TypeScript. The stack also includes TypeScript, GitHub Actions, Node.js.
Active — commit in last 30 days (last push 2026-07-07).
No license information is provided in the README, so you would need to check the repository directly before using it.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.