---
title: "read-package-up 12.0.0: release notes, upgrades and advisories"
description: "read-package-up 12.0.0: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/read-package-up
lang: en
---

[Packages](https://inlinr.com/packages)

# read-package-up

12.0.0 · 7 Nov 2025 MIT 12.7M / week [Repository](https://github.com/sindresorhus/read-package-up) [Homepage](https://github.com/sindresorhus/read-package-up#readme) [npm](https://www.npmjs.com/package/read-package-up) [Atom feed](https://inlinr.com/packages/feed/read-package-up)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/read-package-up/upgrade)

LineNewestSecurity

- 12.x 12.0.0 No known advisory Latest line
- 11.x 11.0.0 No known advisory [To 12.0.0](https://inlinr.com/packages/read-package-up/upgrade/11.0.0-12.0.0)

## What to use instead

## A better maintained package

From the [e18e module-replacements](https://github.com/es-tooling/module-replacements) list, maintained by the community.

The list compares the options for read-package-up: [read the comparison](https://github.com/es-tooling/module-replacements/blob/main/docs/modules/read-package-up.md).

## Before you switch

1. 1  
Check what else depends on it  
Paste your package.json in the [dependency check](https://inlinr.com/tools/dependency-check) to see every deprecated or outdated package in one pass, not only this one.
2. 2  
Read the replacement's peers and releases  
A native API or a few lines of code need no release notes, but check the Node version your project runs on.
3. 3  
Know when it ships  
Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.

## Latest releases

1. 12.x · latest line
2. ### [12.0.0](https://inlinr.com/packages/read-package-up/releases/12.0.0 "Open this release") [](https://github.com/sindresorhus/read-package-up/releases/tag/v12.0.0 "Read this release where it was published")  
7 Nov 2025

  - Breaking  
  Require Node.js 20 [7b5b52a](https://github.com/sindresorhus/read-package-up/commit/7b5b52a)
3. 11.x · maintenance
4. ### [11.0.0](https://inlinr.com/packages/read-package-up/releases/11.0.0 "Open this release") [](https://github.com/sindresorhus/read-package-up/releases/tag/v11.0.0 "Read this release where it was published")  
4 Nov 2023

  - Breaking  
  Rename package from `read-pkg-up` to `read-package-up` [1e22fad](https://github.com/sindresorhus/read-package-up/commit/1e22fad)
  - Breaking  
  Require Node.js 18 [935a546](https://github.com/sindresorhus/read-package-up/commit/935a546)

Dependency tracking

## Know when your own dependencies move

This page watches read-package-up. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health

[Details](https://inlinr.com/packages/read-package-up/security#signals)

- **Provenance**:
- **Publisher**:
- **Maintainers**:
- **Scorecard**:
- **Size**:

## Weekly downloads

Registry facts last checked 22 Nov 2026\. Releases and advisories last read 22 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
