Is rage-edit-tmp safe to use?

rage-edit-tmp has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 40/100 (high risk).

What is the latest version of rage-edit-tmp?

The latest version of rage-edit-tmp is 1.1.0, released 2018-10-11.

Does rage-edit-tmp have known vulnerabilities?

No known vulnerabilities on the latest version of rage-edit-tmp.

Is rage-edit-tmp deprecated?

No, rage-edit-tmp is actively maintained. Latest release: 1.1.0 (2018-10-11).

What are alternatives to rage-edit-tmp?

Popular alternatives to rage-edit-tmp in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does rage-edit-tmp use?

rage-edit-tmp is licensed under MIT.

rage-edit-tmp

npmv1.1.0

🗃 Simple access to, and manipulation of, the Windows Registry. With promises. Without rage.

License MITpermissive1 versions1 maintainers0 deps

MikeKovarik/rage-edit

/ 100

Health

use with caution

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

Moderate health score (40/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/rage-edit-tmp