path-match 1.1.1
wrapper around path-to-regexp for easy route parameters
path-match@1.1.1 was published on 2014-06-11. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
Deprecated: This package is archived and no longer maintained. For support, visit https://github.com/expressjs/express/discussions
All path-match versions · Permanent reference to 1.1.1 · View npm registry JSON · Latest release
Package specifications
| Version | 1.1.1 |
|---|---|
| License declaration | MIT |
| Published | 2014-06-11T22:47:08.115Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 136 |
| Repository forks | 13 |
Install path-match 1.1.1
npm install path-match@1.1.1 pnpm add path-match@1.1.1 yarn add path-match@1.1.1
Runtime dependencies
- path-to-regexp ~0.2.1
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.
- path-to-regexp@0.2.5 — direct
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-Review | 0/10 — Found 1/28 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — project is archived |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Pinned-Dependencies | 3/10 — dependency not pinned by hash detected -- score normalized to 3 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Security-Policy | 9/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-04T15:59:23.315Z
- https://api.deps.dev/v3/systems/npm/packages/path-match/versions/1.1.1 — retrieved 2026-11-04T15:59:23.421Z
- https://api.deps.dev/v3/systems/npm/packages/path-match/versions/1.1.1:dependencies — retrieved 2026-11-04T15:59:23.430Z
- https://api.deps.dev/v3/projects/github.com%2Fpillarjs%2Fpath-match — retrieved 2026-11-03T14:19:52.818Z (stale snapshot; refresh pending)