npmpackage.info

Gathering detailed insights and metrics for get-all-js-files

Gathering detailed insights and metrics for get-all-js-files

get-all-js-files - 1.2.1 | npmpackage.info

get-all-js-files

Get all JS files within a directory. A simple wrapper of node-dir.

1.2.1

JavaScript

Installations

npm install get-all-js-files

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

1.6.2

NPM Version

2.7.1

Score

67.7

Supply Chain

69.8

Quality

75.2

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

1

Closed

0

Merged

1

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Languages

1

JavaScript

JavaScript (100%)

Developer

mrjoelkemp

Download Statistics

Total Downloads

0

Last Day

0

Last Week

0

Last Month

0

Last Year

0

GitHub Statistics

8 Commits

2 Watchers

1 Branches

1 Contributors

Updated on Oct 07, 2014

Maintainers

1

View All 1 Contributors

Package Meta Information

Latest Version

1.2.1

Package Id

get-all-js-files@1.2.1

Size

1.62 kB

NPM Version

2.7.1

Node Version

1.6.2

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

0%

NaN

Compared to previous day

Last Week

0%

NaN

Compared to previous week

Last Month

0%

NaN

Compared to previous month

Last Year

0%

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

1

Dev Dependencies

2

get-all-js-files

This only exists because I used this functionality in numerous projects. It's a simple wrapper of node-dir to get js files from a directory and run callbacks on each file and on traversal completion.

npm install get-all-js-files

Usage

1var getAllJSFiles = require('get-all-js-files');
2
3getAllJSFiles({
4  directory: 'some/path',
5  filesCb: function() {},
6  contentCb: function() {}
7})

`getAllJSFiles(options)`

Options:

directory: the directory where JS files should be found
filesCb: callback to be executed with the list of found files
contentCb: callback to be executed for each file. Should expect filename, fileContent as arguments

Empty State

No vulnerabilities found.

10

Binary-Artifacts

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

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

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

License

Determines if the project has defined a license.

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.

Score

2.6

/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.