npmpackage.info

Gathering detailed insights and metrics for @types/connect-history-api-fallback-exclusions

@types/connect-history-api-fallback-exclusions

The repository for high quality TypeScript type definitions.

1.5.5

49,132

NOASSERTION

TypeScript

4.60 kB

19,542 6.9

Installations

npm install @types/connect-history-api-fallback-exclusions

Developer Guide

BETA

Typescript

Yes

Module System

N/A

Score

64.2

Supply Chain

74.8

Quality

75.4

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

160

Total

60,660

Closed

9,570

Merged

50,930

Issues

Open

563

Total

8,074

Closed

7,511

Releases

0.1.450

Published on 04 Sept 2019

View all 1 releases

Contributors

9,978

View all 9,978 contributors

Languages

TypeScript

JavaScript

Shell

TypeScript (99.9%)

JavaScript (0.09%)

Shell (0.01%)

Love this project? Help keep it running — sponsor us today! 🚀

Developer

DefinitelyTyped

Download Statistics

Total Downloads

19,542

Last Day

Last Week

Last Month

157

Last Year

1,365

GitHub Statistics

49,132 Stars

88,662 Commits

30,297 Forks

640 Watching

5 Branches

9,978 Contributors

Maintainers

Package Meta Information

Latest Version

1.5.5

Package Id

@types/connect-history-api-fallback-exclusions@1.5.5

Unpacked Size

4.60 kB

Size

1.88 kB

File Count

Publised On

07 Nov 2023

Total Downloads

Cumulative downloads

Total Downloads

19,542

Last day

-85.7%

Compared to previous day

Last week

-54.8%

Compared to previous week

Last month

65.3%

157

Compared to previous month

Last year

-36.1%

1,365

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

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

Versions

Installation

npm install --save @types/connect-history-api-fallback-exclusions

Summary

This package contains type definitions for connect-history-api-fallback-exclusions (https://github.com/Wirewheel/connect-history-api-fallback#readme).

Details

Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/connect-history-api-fallback-exclusions.

index.d.ts

1/// <reference types="node" />
2
3import { Url } from "url";
4
5import * as core from "express-serve-static-core";
6
7declare function historyApiFallback(options?: historyApiFallback.Options): core.RequestHandler;
8
9declare namespace historyApiFallback {
10    interface Options {
11        exclusions?: string[] | undefined;
12        disableDotRule?: true | undefined;
13        htmlAcceptHeaders?: string[] | undefined;
14        index?: string | undefined;
15        logger?: typeof console.log | undefined;
16        rewrites?: Rewrite[] | undefined;
17        verbose?: boolean | undefined;
18    }
19
20    interface Context {
21        match: RegExpMatchArray;
22        parsedUrl: Url;
23    }
24    type RewriteTo = (context: Context) => string;
25
26    interface Rewrite {
27        from: RegExp;
28        to: string | RegExp | RewriteTo;
29    }
30}
31export = historyApiFallback;
32

Additional Details

Last updated: Mon, 06 Nov 2023 22:41:05 GMT
Dependencies: @types/express-serve-static-core, @types/node

Credits

These definitions were written by Tony Stone.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

9

License

Determines if the project has defined a license.

8

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

8

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

SAST

Determines if the project uses static code analysis.

0

Fuzzing

Determines if the project uses fuzzing.

Score

6.9

/10

Last Scanned on 2025-02-03

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More