Is continued-quiet-previous-touch safe to use?

continued-quiet-previous-touch has no known vulnerabilities on the latest version (). DepScope rates its health at 0/100 (unknown risk).

What is the latest version of continued-quiet-previous-touch?

The latest version of continued-quiet-previous-touch is .

Does continued-quiet-previous-touch have known vulnerabilities?

No known vulnerabilities on the latest version of continued-quiet-previous-touch.

Is continued-quiet-previous-touch deprecated?

No, continued-quiet-previous-touch is actively maintained. Latest release: .

What are alternatives to continued-quiet-previous-touch?

Popular alternatives to continued-quiet-previous-touch in npm include: ?, debug, ansi-styles, brace-expansion, semver.

What license does continued-quiet-previous-touch use?

License information for continued-quiet-previous-touch is not declared in the registry metadata.

continued-quiet-previous-touch

npmv

0 versions0 deps

/ 100

Health

insufficient data

continued-quiet-previous-touch has limited data (1/6 signals) — verify manually before use

Limited information available for this package
Moderate health score (31/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

0/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/continued-quiet-previous-touch