npmpackage.info

Gathering detailed insights and metrics for parent-package-json

Other packages similar to parent-package-json

pkg-dir

9.0.0

Find the root directory of a Node.js project or npm package

read-pkg-up

11.0.0

Read the closest package.json file

find-package-json

1.2.0

Find package.json files in parent directories, keep finding until you find the right one using iterators.

fd-package-json

2.0.0

Utilities for finding the closest package.json file

Gathering detailed insights and metrics for parent-package-json

parent-package-json - 3.0.0 | npmpackage.info

parent-package-json

Find the parent package.json

3.0.0

ISC

TypeScript

7.15 kB

Installations

npm install parent-package-json

Developer Guide

BETA

Typescript

No

Module System

ESM

Min. Node Version

>= 18.0.0

Pull Requests

Open

0

Total

67

Closed

48

Merged

19

Issues

Open

0

Total

2

Closed

2

Releases

v3.0.0

Updated on Jun 10, 2023

v2.0.0

Updated on Aug 16, 2016

v1.1.0

Updated on Jan 09, 2016

v1.0.3

Updated on Jan 08, 2016

v1.0.2

Updated on Jan 08, 2016

v1.0.1

Updated on Jan 08, 2016

View All 7 releases

Languages

TypeScript

TypeScript (100%)

Developer

maxrimue

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

ISC License

6 Stars

88 Commits

2 Forks

1 Watchers

19 Branches

3 Contributors

Updated on Oct 17, 2023

Maintainers

View All 3 Contributors

Package Meta Information

Latest Version

3.0.0

Package Id

parent-package-json@3.0.0

Unpacked Size

7.15 kB

Size

2.99 kB

File Count

Published on

Jun 10, 2023

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

@types/node rome typescript vitest

parent-package-json

Find, read and parse the package.json that sits above your module. Provide a custom ignore count or start path to define where to look for a parent package.

1npm install --save parent-package-json

1import parentJSON from "parent-package-json";

Getting Started

To get the nearest parent package.jsons path, content (as string) or parsed content (using JSON.parse):

1const parent = parentJSON();
2
3const pathToParentPackageJSON = parent.path.relative;
4const parentContentAsString = parent.read();
5const parentContentAsObject = parent.parse();
6
7const parentVersion = parentContentAsObject.version;

The parent package.json is looked up starting from the current working directory of your script. If none is found, paths, .read() and .parse() will return undefined.

Custom Path and Ignore Count

If you need to determine the parent package.json of a custom path instead of the current working directory, which should be the module from which you are running the code, you can specify it via the path option:

1const startPath = path.join(...);
2const parent = parent({ startPath });

You can also specify a count of parent directories to skip:

1const parent = parent({ ignoreCount: 1 });

Note: A package.json file in the provided startPath is always ignored. Set the startPath one layer below the one where you expect to find a parent package file.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More