Gathering detailed insights and metrics for make-empty-dir
Gathering detailed insights and metrics for make-empty-dir
Installations
npm install make-empty-dirDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Min. Node Version
>=18.12
Node Version
20.11.1
NPM Version
10.8.1
Score
92.5
Supply Chain
78.7
Quality
78
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Languages
2
JavaScript
TypeScript
JavaScript (77.07%)
TypeScript (22.93%)
Developer
zkochan
Download Statistics
Total Downloads
747,481
Last Day
636
Last Week
14,522
Last Month
68,286
Last Year
262,759
GitHub Statistics
MIT License
102 Stars
440 Commits
28 Forks
4 Watchers
30 Branches
22 Contributors
Updated on Jun 13, 2025
Bundle Size
1.08 kB
Minified
433.00 B
Minified + Gzipped
Maintainers
1
Package Meta Information
Latest Version
3.0.2
Package Id
make-empty-dir@3.0.2
Unpacked Size
4.33 kB
Size
2.05 kB
File Count
5
NPM Version
10.8.1
Node Version
20.11.1
Published on
Jul 04, 2024
Total Downloads
Cumulative downloads
Total Downloads
747,481
Last Day
-17.9%
636
Compared to previous day
Last Week
-16.3%
14,522
Compared to previous week
Last Month
47.6%
68,286
Compared to previous month
Last Year
30.8%
262,759
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
make-empty-dir
Ensures that a directory is empty
Ensures that a directory is empty. Deletes directory contents if the directory is not empty. If the directory does not exist, it is created. The directory itself is not deleted.
It works faster than emptyDir() of fs-extra because the contents of the directory are not read before the creation of the directory.
Installation
1<npm|yarn|pnpm> add make-empty-dir
Usage
1'use strict' 2const makeEmptyDir = require('make-empty-dir') 3 4await makeEmptyDir('dir-name') 5 6// or create the parent dir as well 7await makeEmptyDir('dir/subdir', { recursive: true })
API
makeEmptyDir(dir: string, [opts]): Promise<'created' | 'emptied'>
Arguments:
dir- Path - the path of the directory.opts.recursive- Boolean - Optional. If true, parent directories will be created.
Returns:
A string is returned.
'created'- if there was no directory'emptied'- if there was a directory and the its contents were removed.
License
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 8/30 approved changesets -- score normalized to 2
Reason
3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/zkochan/packages/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/zkochan/packages/ci.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/zkochan/packages/ci.yml/main?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 8 are checked with a SAST tool
Reason
15 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-v9mx-4pqq-h232
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-h6ch-v84p-w6p9
- Warn: Project is vulnerable to: GHSA-ff7x-qrg7-qggm
- Warn: Project is vulnerable to: GHSA-pfrx-2q88-qq97
- Warn: Project is vulnerable to: GHSA-9c47-m6qq-7p4h
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-w5p7-h5w8-2hfq
- Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
Score
2.9
/10
Last Scanned on 2025-06-09
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