jayson 1.1.1
JSON-RPC 1.0/2.0 compliant server and client
jayson@1.1.1 was published on 2014-05-10. Its manifest declares 4 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.4.0.
All jayson versions · Permanent reference to 1.1.1 · Latest release
Package specifications
| Version | 1.1.1 |
|---|---|
| License declaration | Not declared |
| Published | 2014-05-10T10:13:17.586Z |
| Node.js requirement | >= 0.4.0 |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| 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 | index |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 727 |
| Repository forks | 115 |
Install jayson 1.1.1
npm install jayson@1.1.1 pnpm add jayson@1.1.1 yarn add jayson@1.1.1
Runtime dependencies
- eyes 0.1.8
- commander 1.3.2
- JSONStream 0.8.0
- underscore ^1.6.0
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.
- JSONStream@0.8.0 — direct
- commander@1.3.2 — direct
- eyes@0.1.8 — direct
- jsonparse@0.0.5 — indirect
- keypress@0.1.0 — indirect
- through@2.2.7 — indirect
- underscore@1.13.8 — 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 0/20 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- 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 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| 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/jayson/1.1.1 — retrieved 2026-10-29T18:24:10.959Z
- https://api.deps.dev/v3/projects/github.com%2Ftedeh%2Fjayson — retrieved 2026-10-29T17:25:45.618Z
- https://api.deps.dev/v3/systems/npm/packages/jayson/versions/1.1.1 — retrieved 2026-10-29T18:24:11.804Z
- https://api.deps.dev/v3/systems/npm/packages/jayson/versions/1.1.1:dependencies — retrieved 2026-10-29T18:24:11.933Z