npmpackage.info

Gathering detailed insights and metrics for mkdirp-infer-owner

mkdirp-infer-owner - 2.0.0 | npmpackage.info

mkdirp-infer-owner

mkdirp, but chown to the owner of the containing folder if possible and necessary

2.0.0

ISC

JavaScript

1.7

Installations

npm install mkdirp-infer-owner

Developer Guide

BETA

Typescript

No

Module System

N/A

Min. Node Version

>=10

Node Version

14.2.0

NPM Version

6.14.5 Pull Requests

Open

10

Total

12

Closed

2

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

isaacs

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

ISC License

1 Stars

14 Commits

2 Forks

2 Watchers

11 Branches

1 Contributors

Updated on May 08, 2021

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

2.0.0

Package Id

mkdirp-infer-owner@2.0.0

Size

1.64 kB

NPM Version

6.14.5

Node Version

14.2.0

Published on

Jul 11, 2020

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

Dependencies

chownr infer-owner mkdirp

Dev Dependencies

require-inject tap

mkdirp-infer-owner

mkdirp, but chown to the owner of the containing folder if possible and necessary.

That is, on Windows and when running as non-root, it's exactly the same as mkdirp.

When running as root on non-Windows systems, it uses infer-owner to find the owner of the containing folder, and then chownr to set the ownership of the created folder to that same uid/gid.

This is used by npm to prevent root-owned files and folders from showing up in your home directory (either in node_modules or in the ~/.npm cache) when running as root.

No vulnerabilities found.

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.

0

Code-Review

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

0

SAST

Determines if the project uses static code analysis.

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

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Security-Policy

Determines if the project has published a security policy.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.7

/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