to-regex-range 4.0.3

Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

to-regex-range@4.0.3 was published on 2019-01-17. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.0.

All to-regex-range versions · Permanent reference to 4.0.3 · Latest release

Package specifications

Version4.0.3
License declarationMIT
Published2019-01-17T20:53:36.504Z
Node.js requirement>=4.0
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size21.34 KiB
Published file count4
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars173
Repository forks23

Install to-regex-range 4.0.3

npm install to-regex-range@4.0.3
pnpm add to-regex-range@4.0.3
yarn add to-regex-range@4.0.3

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review0/10 — Found 2/25 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected

Evidence and freshness