Is @natlibfi/loglevel-message-prefix safe to use?

@natlibfi/loglevel-message-prefix has no known vulnerabilities on the latest version (3.0.1). DepScope rates its health at 37/100 (critical risk).

What is the latest version of @natlibfi/loglevel-message-prefix?

The latest version of @natlibfi/loglevel-message-prefix is 3.0.1, released 2017-07-02.

Does @natlibfi/loglevel-message-prefix have known vulnerabilities?

No known vulnerabilities on the latest version of @natlibfi/loglevel-message-prefix.

Is @natlibfi/loglevel-message-prefix deprecated?

No, @natlibfi/loglevel-message-prefix is actively maintained. Latest release: 3.0.1 (2017-07-02).

What are alternatives to @natlibfi/loglevel-message-prefix?

Popular alternatives to @natlibfi/loglevel-message-prefix in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does @natlibfi/loglevel-message-prefix use?

@natlibfi/loglevel-message-prefix is licensed under MIT.

@natlibfi/loglevel-message-prefix

npmv3.0.1

Plugin for loglevel which allows defining prefixes for log messages

License MITpermissive1 versions2 deps

ssh://[email protected]/NatLibFi/loglevel-message-prefix

/ 100

Health

use with caution

@natlibfi/[email protected] low health (37/100) — consider alternatives

Low health score (37/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

loglevel @natlibfi/es6-polyfills

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@natlibfi/loglevel-message-prefix