Installations

npm install lws-blacklist

Score

99.1

Supply Chain

63.8

Quality

75.7

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

1

Closed

1

Issues

Open

0

Total

1

Closed

1

Releases

Unable to fetch releases

Developer

lwsjs

Developer Guide

BETA

Module System

Unable to determine the module system for this package.

Min. Node Version

>=10

Typescript Support

No

Node Version

13.8.0

NPM Version

6.13.7 Statistics

1 Stars

30 Commits

1 Forks

3 Watching

1 Branches

1 Contributors

Updated on 11 Sept 2024

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

14,142,208

Last day

-50.7%

9,908

Compared to previous day

Last week

-31%

67,733

Compared to previous week

Last month

4.6%

380,644

Compared to previous month

Last year

14.3%

3,348,602

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

2

array-back path-to-regexp

Dev Dependencies

3

lws node-fetch test-runner

Versions

lws-blacklist

Middleware for lws enabling certain routes to be forbidden. See here for usage instructions.

Adds the following options to lws.

--blacklist path ...           A list of routes to forbid, e.g. `--blacklist "/admin/(.*)" "(.*).php"`

No vulnerabilities found.

10

Binary-Artifacts

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

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

1

Maintained

Determines if the project is "actively maintained".

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

SAST

Determines if the project uses static code analysis.

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

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.

Score

3.5

/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