Is re-define-module safe to use?

re-define-module has no known vulnerabilities on the latest version (0.1.2). DepScope rates its health at 42/100 (high risk).

What is the latest version of re-define-module?

The latest version of re-define-module is 0.1.2, released 2014-09-16.

Does re-define-module have known vulnerabilities?

No known vulnerabilities on the latest version of re-define-module.

Is re-define-module deprecated?

No, re-define-module is actively maintained. Latest release: 0.1.2 (2014-09-16).

What are alternatives to re-define-module?

Popular alternatives to re-define-module in npm include: minimatch, lru-cache, chalk, commander, @types/node.

What license does re-define-module use?

re-define-module is licensed under MIT.

re-define-module

npmv0.1.2

re-define-module ================

License MITpermissive4 versions1 maintainers2 deps83 weekly dl

/ 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

32.2 KBminified

11.1 KB gzipped

2 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

vinyl lodash

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/re-define-module