npmpackage.info

Gathering detailed insights and metrics for @types/range-parser

Other packages similar to @types/range-parser

pg-range-parser

1.0.0

Parses postgres range types

json-parse-ast

1.0.8

Just another custom JSON AST parser, but this time with position/range types compatible with monaco's API

Gathering detailed insights and metrics for @types/range-parser

@types/range-parser - 1.2.7 | npmpackage.info

@types/range-parser

The repository for high quality TypeScript type definitions.

1.2.7

50,028

NOASSERTION

TypeScript

4.51 kB

Installations

npm install @types/range-parser

Developer Guide

BETA

Typescript

Yes

Module System

N/A

Pull Requests

Open

150

Total

61,817

Closed

9,749

Merged

51,918

Issues

Open

565

Total

8,085

Closed

7,520

Releases

0.1.450

Updated on Sep 04, 2019

View All 1 releases

Languages

TypeScript

JavaScript

Shell

TypeScript (99.84%)

JavaScript (0.15%)

Shell (0.01%)

Developer

DefinitelyTyped

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

NOASSERTION License

50,028 Stars

89,737 Commits

30,433 Forks

640 Watchers

6 Branches

9,957 Contributors

Updated on Jul 13, 2025

Maintainers

View All 9,957 Contributors

Package Meta Information

Latest Version

1.2.7

Package Id

@types/range-parser@1.2.7

Unpacked Size

4.51 kB

Size

1.93 kB

File Count

Published on

Nov 07, 2023

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Installation

npm install --save @types/range-parser

Summary

This package contains type definitions for range-parser (https://github.com/jshttp/range-parser).

Details

Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/range-parser.

index.d.ts

1/**
2 * When ranges are returned, the array has a "type" property which is the type of
3 * range that is required (most commonly, "bytes"). Each array element is an object
4 * with a "start" and "end" property for the portion of the range.
5 *
6 * @returns `-1` when unsatisfiable and `-2` when syntactically invalid, ranges otherwise.
7 */
8declare function RangeParser(
9    size: number,
10    str: string,
11    options?: RangeParser.Options,
12): RangeParser.Result | RangeParser.Ranges;
13
14declare namespace RangeParser {
15    interface Ranges extends Array<Range> {
16        type: string;
17    }
18    interface Range {
19        start: number;
20        end: number;
21    }
22    interface Options {
23        /**
24         * The "combine" option can be set to `true` and overlapping & adjacent ranges
25         * will be combined into a single range.
26         */
27        combine?: boolean | undefined;
28    }
29    type ResultUnsatisfiable = -1;
30    type ResultInvalid = -2;
31    type Result = ResultUnsatisfiable | ResultInvalid;
32}
33
34export = RangeParser;
35

Additional Details

Last updated: Tue, 07 Nov 2023 09:09:39 GMT
Dependencies: none

Credits

These definitions were written by Tomek Łaziuk.

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

Code-Review

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

9

License

Determines if the project has defined a license.

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

7

/10

Last Scanned on 2025-07-07

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