Installations

npm install parent-package-json

Pull Requests

Open

0

Total

67

Closed

48

Merged

19

Issues

Open

0

Total

2

Closed

2

Releases

7

v3.0.0

Published on 10 Jun 2023

v2.0.0

Published on 16 Aug 2016

v1.1.0

Published on 09 Jan 2016

v1.0.3

Published on 08 Jan 2016

v1.0.2

Published on 08 Jan 2016

v1.0.1

Published on 08 Jan 2016

View all 7 releases

Developer

maxrimue

Developer Guide

BETA

Module System

ESM

Min. Node Version

>= 18.0.0

Typescript Support

No

Node Version

NPM Version

Statistics

6 Stars

88 Commits

2 Forks

2 Watching

19 Branches

3 Contributors

Updated on 17 Oct 2023

Bundle Size

847.00 B

Minified

471.00 B

Minified + Gzipped

Bundlephobia

Languages

TypeScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

1,832,901

Last day

-24.9%

730

Compared to previous day

Last week

-8.4%

4,782

Compared to previous week

Last month

-0.7%

23,422

Compared to previous month

Last year

-23.1%

560,567

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

4

@types/node rome typescript vitest

Versions

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.

2

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Maintained

Determines if the project is "actively maintained".

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

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.

Score

3.2

/10

Last Scanned on 2024-11-18

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