Is largest-semantic-change safe to use?

largest-semantic-change has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 45/100 (high risk).

What is the latest version of largest-semantic-change?

The latest version of largest-semantic-change is 1.1.0, released 2018-02-15.

Does largest-semantic-change have known vulnerabilities?

No known vulnerabilities on the latest version of largest-semantic-change.

Is largest-semantic-change deprecated?

No, largest-semantic-change is actively maintained. Latest release: 1.1.0 (2018-02-15).

What are alternatives to largest-semantic-change?

Popular alternatives to largest-semantic-change in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does largest-semantic-change use?

largest-semantic-change is licensed under MIT.

largest-semantic-change

npmv1.1.0

Given a list of semantic commit changes, returns the largest one

License MITpermissive2 versions1 maintainers2 deps1,036 weekly dl

bahmutov/largest-semantic-change

/ 100

Health

use with caution

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

Moderate health score (45/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

check-more-types lazy-ass

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/largest-semantic-change