pkg.soopen package index

brew / rank 6313

Install patch-package with Homebrew, Nix

Fix broken node modules instantly. Version 8.0.1 via Homebrew; verified from local package data. Also installable with nix: nix profile install nixpkgs#patch-package.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified · 100%
brew install patch-package

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#patch-package

nixpkgs package indexes · pkgs/by-name/pa/patch-package/package.nix · source: api.github.com

overview

Package summary

Fix broken node modules instantly

Commands and aliases

  • patch-package

history

Project history and usage

patch-package creates versioned diff files from local changes to Node.js dependencies and reapplies them after dependency installation.

Project history

patch-package was created for JavaScript application authors who needed to preserve fixes made inside installed npm dependencies. The project evolved beyond basic patch creation and application to support nested packages, dev-only patches, ordered patch sequences, rebasing, partial application, reverse application, CI behavior, and alternate patch directories.

Adoption history

The project became a widely used workaround in npm and Yarn applications because it lets teams version local dependency fixes without publishing a fork. Its official repository documents automatic application through package-manager lifecycle hooks and has accumulated substantial community use.

How it is used

A developer edits an installed dependency under node_modules and runs patch-package for that package. The tool writes a versioned patch under the application's patches directory; the patch is committed with the application and normally reapplied from a postinstall script. Teams should keep patches focused and reassess them when dependency versions change.

Why package nerds care

patch-package formalized a pragmatic pattern familiar to package maintainers: carry a small downstream patch while waiting for upstream. It makes those changes visible in ordinary code review and reproducible on developer machines and CI, occupying a useful middle ground between directly editing node_modules and maintaining a permanent fork.

Timeline

  • The project expanded from basic dependency patches to CI-aware application, dev-only patches, partial application, and ordered patch sequences.

Related projects

  • The project integrates with npm and Yarn workflows. Its documentation also discusses postinstall-postinstall for older Yarn lifecycle behavior and contrasts its workflow with maintaining dependency forks.

Sources

  • Official changelog: https://github.com/ds300/patch-package/blob/master/CHANGELOG.md
  • Official releases: https://github.com/ds300/patch-package/releases
  • Official repository and README: https://github.com/ds300/patch-package

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
<project>/package.json
Windows
<project>\package.json

executables

Installed executables

CommandKindExposureNote
patch-packagecliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-09-19
manager version8.0.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/ds300/patch-package

install metadata

Package metadata

Package keybrew:patch-package
Version8.0.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/patch-package
Homepagehttps://github.com/ds300/patch-package
Repositoryhttps://github.com/ds300/patch-package
LicenseMIT
Source archivehttps://registry.npmjs.org/patch-package/-/patch-package-8.0.1.tgz
Dependenciesnode
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namepatch-package
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

patch-package

nix profile install nixpkgs#patch-package
  • normalized package name match
  • Matched by: Patch Package
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/pa/patch-package/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

Related tools

  • nodeRuntime dependency declared by Homebrew.

Same workflow

  • npm-check-updatesShares pkgdb curated category or tags: cli, dependencies, developer-tools, nodejs, npm.
  • nrmShares pkgdb curated category or tags: cli, developer-tools, nodejs, npm, package-management.
  • pnpmShares pkgdb curated category or tags: cli, dependencies, developer-tools, nodejs, package-management.
  • corepackShares pkgdb curated category or tags: cli, developer-tools, nodejs, npm, package-management.
  • niShares pkgdb curated category or tags: cli, developer-tools, nodejs, npm, package-management.
  • pipxShares pkgdb curated category or tags: cli, developer-tools, package-management.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation