Is @types/connect-history-api-fallback safe to use?

@types/connect-history-api-fallback has no known vulnerabilities on the latest version (1.5.4). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @types/connect-history-api-fallback?

The latest version of @types/connect-history-api-fallback is 1.5.4, released 2023-11-20.

Does @types/connect-history-api-fallback have known vulnerabilities?

No known vulnerabilities on the latest version of @types/connect-history-api-fallback.

Is @types/connect-history-api-fallback deprecated?

No, @types/connect-history-api-fallback is actively maintained. Latest release: 1.5.4 (2023-11-20).

What are alternatives to @types/connect-history-api-fallback?

Popular alternatives to @types/connect-history-api-fallback in npm include: debug, picomatch, @types/node, source-map, react-is.

What license does @types/connect-history-api-fallback use?

@types/connect-history-api-fallback is licensed under MIT.

@types/connect-history-api-fallback

npmv1.5.4

TypeScript definitions for connect-history-api-fallback

License MITpermissive11 versions1 maintainers2 deps

DefinitelyTyped/DefinitelyTyped

/ 100

Health

use with caution

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

Low health score (39/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Quality signals

Download trend

stable(0%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (2)

@types/node @types/express-serve-static-core

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@types/connect-history-api-fallback