Is express-force-ssl safe to use?

express-force-ssl has no known vulnerabilities on the latest version (0.3.2). DepScope rates its health at 43/100 (high risk).

What is the latest version of express-force-ssl?

The latest version of express-force-ssl is 0.3.2, released 2016-05-12.

Does express-force-ssl have known vulnerabilities?

No known vulnerabilities on the latest version of express-force-ssl.

Is express-force-ssl deprecated?

No, express-force-ssl is actively maintained. Latest release: 0.3.2 (2016-05-12).

What are alternatives to express-force-ssl?

Popular alternatives to express-force-ssl in npm include: semver, minimatch, ansi-styles, debug, brace-expansion.

What license does express-force-ssl use?

License information for express-force-ssl is not declared in the registry metadata.

express-force-ssl

npmv0.3.2

Force SSL on particular/all pages in Express

19 versions1 maintainers1 deps

battlejj/express-force-ssl

/ 100

Health

use with caution

[email protected] low health (43/100) — consider alternatives

Moderate health score (43/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

lodash.assign

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/express-force-ssl