regexparam 1.2.0
A tiny (285B) utility that converts route patterns into RegExp. Limited alternative to `path-to-regexp` 🙇
regexparam@1.2.0 was published on 2019-03-10. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.
All regexparam versions · Permanent reference to 1.2.0 · Latest release
Package specifications
| Version | 1.2.0 |
|---|---|
| License declaration | MIT |
| Published | 2019-03-10T00:00:17.424Z |
| Node.js requirement | >=6 |
| Type declarations | Not declared |
| Runtime dependency count | 0 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 6.95 KiB |
| Published file count | 5 |
| Package type | Not declared |
| ES module entry | dist/regexparam.mjs |
| Default entry | dist/regexparam.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | 598 |
| Repository forks | 27 |
Install regexparam 1.2.0
npm install regexparam@1.2.0 pnpm add regexparam@1.2.0 yarn add regexparam@1.2.0
Runtime dependencies
- None declared
Peer requirements
- None declared
Optional dependencies
- None declared
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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Code-Review | 2/10 — Found 4/19 approved changesets -- score normalized to 2 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/regexparam/1.2.0 — retrieved 2026-10-31T19:24:28.965Z
- https://api.deps.dev/v3/projects/github.com%2Flukeed%2Fregexparam — retrieved 2026-10-31T17:00:24.734Z