parambulator 1.5.2
A simple way to generate nice error messages for named parameters.
parambulator@1.5.2 was published on 2016-05-08. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All parambulator versions · Permanent reference to 1.5.2 · Latest release
Package specifications
| Version | 1.5.2 |
|---|---|
| License declaration | Not declared |
| Published | 2016-05-08T22:03:05.748Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| 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 | parambulator.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 40 |
| Repository forks | 12 |
Install parambulator 1.5.2
npm install parambulator@1.5.2 pnpm add parambulator@1.5.2 yarn add parambulator@1.5.2
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.
- gex@0.2.2 — direct
- jsonic@0.2.2 — direct
- lodash@3.10.0 — indirect
- lodash@4.5.0 — 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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 0/29 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| 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/parambulator/1.5.2 — retrieved 2026-10-29T23:21:22.951Z
- https://api.deps.dev/v3/systems/npm/packages/parambulator/versions/1.5.2:dependencies — retrieved 2026-10-29T22:35:16.655Z
- https://api.deps.dev/v3/systems/npm/packages/parambulator/versions/1.5.2 — retrieved 2026-10-29T22:35:16.632Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Frjrodger%2Fparambulator — retrieved 2026-10-29T22:35:16.813Z