Is connect-history-api-fallback safe to use?

connect-history-api-fallback has no known vulnerabilities on the latest version (2.0.0). DepScope rates its health at 67/100 (moderate risk).

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

The latest version of connect-history-api-fallback is 2.0.0, released 2022-06-27.

Does connect-history-api-fallback have known vulnerabilities?

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

Is connect-history-api-fallback deprecated?

No, connect-history-api-fallback is actively maintained. Latest release: 2.0.0 (2022-06-27).

What are alternatives to connect-history-api-fallback?

Popular alternatives to connect-history-api-fallback in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does connect-history-api-fallback use?

connect-history-api-fallback is licensed under MIT.

connect-history-api-fallback

npmv2.0.0

Provides a fallback for non-existing directories so that the HTML 5 history API can be used.

License MITpermissive13 versions1 maintainers0 deps18,221,070 weekly dl

bripkens/connect-history-api-fallback

/ 100

Health

use with caution

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

Moderate health score (67/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

15/15

maturity

7/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.8 KBminified

0.8 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

7/10typed

Types from @types/connect-history-api-fallback (DefinitelyTyped)

Quality signals

Download trend

stable(0%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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