Is chrome-https safe to use?

chrome-https has no known vulnerabilities on the latest version (2.0.1). DepScope rates its health at 42/100 (high risk).

What is the latest version of chrome-https?

The latest version of chrome-https is 2.0.1, released 2016-10-31.

Does chrome-https have known vulnerabilities?

No known vulnerabilities on the latest version of chrome-https.

Is chrome-https deprecated?

No, chrome-https is actively maintained. Latest release: 2.0.1 (2016-10-31).

What are alternatives to chrome-https?

Popular alternatives to chrome-https in npm include: minimatch, lru-cache, chalk, commander, @types/node.

What license does chrome-https use?

chrome-https is licensed under MIT/X11.

chrome-https

npmv2.0.1

https module compatability for chrome apps

License MIT/X11permissive3 versions1 maintainers6 deps10 weekly dl

No9/chrome-https

/ 100

Health

safe to use

[email protected] is safe to use (health: 42/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.2 KBminified

0.1 KB gzipped

6 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (6)

builtin-status-codes foreach indexof inherits object-keys xtend

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/chrome-https