npmpackage.info

Gathering detailed insights and metrics for @appgeist/ensure-dir

Other packages similar to @appgeist/ensure-dir

@types/appgeist__ensure-dir

1.1.2

TypeScript definitions for @appgeist/ensure-dir

Gathering detailed insights and metrics for @appgeist/ensure-dir

@appgeist/ensure-dir - 1.1.4 | npmpackage.info

@appgeist/ensure-dir

Utility function to ensure a directory path exists and return a Promise

1.1.4

ISC

JavaScript

602.00 B

6,228 1.7

Installations

npm install @appgeist/ensure-dir

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Pull Requests

Open

5

Total

7

Closed

1

Merged

1

Issues

Open

3

Total

3

Closed

0

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

appgeist

Download Statistics

Total Downloads

6,228

Last Day

Last Week

Last Month

130

Last Year

987

GitHub Statistics

ISC License

3 Stars

26 Commits

6 Branches

1 Contributors

Updated on Jun 06, 2022

Bundle Size

1.13 kB

Minified

602.00 B

Minified + Gzipped

Bundlephobia

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

1.1.4

Package Id

@appgeist/ensure-dir@1.1.4

Unpacked Size

2.99 kB

Size

1.65 kB

File Count

Total Downloads

Cumulative downloads

Total Downloads

6,228

Last Day

-78.6%

Compared to previous day

Last Week

-28.6%

Compared to previous week

Last Month

154.9%

130

Compared to previous month

Last Year

-25.8%

987

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

mkdirp

Dev Dependencies

@appgeist/eslint-config-base

@appgeist/ensure-dir

Utility function to ensure a directory path exists and return a Promise. Uses mkdirp under the hood.

Usage

1const ensureDir = require("@appgeist/ensure-dir");
2
3await ensureDir("/folder/to/store/lotsa/files");

Why not mkdirp-promise?

@appgeist/ensure-dir should be slightly more efficient than mkdirp-promise because it checks whether the specified path exists before trying to create it.

License

The ISC License.

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

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

Branch-Protection

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

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.7

/10

Last Scanned on 2025-03-31

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