Is @gkalpak/ng-pr-merge safe to use?

@gkalpak/ng-pr-merge has no known vulnerabilities on the latest version (0.0.36). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @gkalpak/ng-pr-merge?

The latest version of @gkalpak/ng-pr-merge is 0.0.36, released 2021-07-22.

Does @gkalpak/ng-pr-merge have known vulnerabilities?

No known vulnerabilities on the latest version of @gkalpak/ng-pr-merge.

Is @gkalpak/ng-pr-merge deprecated?

No, @gkalpak/ng-pr-merge is actively maintained. Latest release: 0.0.36 (2021-07-22).

What are alternatives to @gkalpak/ng-pr-merge?

Popular alternatives to @gkalpak/ng-pr-merge in npm include: ?, minimatch, ansi-styles, brace-expansion, semver.

What license does @gkalpak/ng-pr-merge use?

@gkalpak/ng-pr-merge is licensed under Unlicense.

@gkalpak/ng-pr-merge

npmv0.0.36

A utility for rebase-merging (AngularJS-related) GitHub PRs.

License Unlicensepermissive31 versions1 maintainers3 deps33 weekly dl

gkalpak/ng-pr-merge

/ 100

Health

use with caution

@gkalpak/[email protected] low health (39/100) — consider alternatives

Moderate health score (39/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/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 (3)

@gkalpak/ng-cla-check @gkalpak/ng-maintain-utils chalk

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@gkalpak/ng-pr-merge