json-future 1.1.3
Unbelievable and Modern JSON interface.
json-future@1.1.3 was published on 2016-01-28. Its manifest declares 11 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.10.0.
All json-future versions · Permanent reference to 1.1.3 · Latest release
Package specifications
| Version | 1.1.3 |
|---|---|
| License declaration | MIT |
| Published | 2016-01-28T16:04:04.296Z |
| Node.js requirement | >= 0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 11 |
| 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.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 47 |
| Repository stars | 54 |
| Repository forks | 2 |
Install json-future 1.1.3
npm install json-future@1.1.3 pnpm add json-future@1.1.3 yarn add json-future@1.1.3
Runtime dependencies
- args-js ~0.10.11
- nodeify ~1.0.0
- wrap-sync ~1.0.0
- cb2promise ~1.0.2
- coffeelint ~1.14.2
- parse-json ~2.2.0
- coffee-script ~1.10.0
- async.wrapsync ~1.0.2
- load-json-file ~1.1.0
- write-json-file ~1.2.0
- json-stringify-safe ~5.0.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.
- args-js@0.10.12 — direct
- async.wrapsync@1.0.2 — direct
- balanced-match@1.0.2 — indirect
- brace-expansion@1.1.21 — indirect
- cb2promise@1.0.7 — direct
- coffee-script@1.10.0 — direct
- coffeelint@1.14.2 — direct
- concat-map@0.0.1 — indirect
- error-ex@1.3.4 — indirect
- glob@4.5.3 — indirect
- graceful-fs@4.2.11 — indirect
- ignore@2.2.19 — indirect
- imurmurhash@0.1.4 — indirect
- inflight@1.0.6 — indirect
- inherits@2.0.4 — indirect
- is-arrayish@0.2.1 — indirect
- is-plain-obj@1.1.0 — indirect
- is-promise@1.0.1 — indirect
- is-utf8@0.2.1 — indirect
- json-stringify-safe@5.0.1 — direct
- load-json-file@1.1.0 — direct
- lodash.isobject@3.0.2 — indirect
- lodash.restparam@3.6.1 — indirect
- minimatch@2.0.10 — indirect
- minimist@0.0.10 — indirect
- minimist@1.2.8 — indirect
- mkdirp@0.5.6 — indirect
- nodeify@1.0.1 — direct
- object-assign@4.1.1 — indirect
- once@1.4.0 — indirect
- optimist@0.6.1 — indirect
- parse-json@2.2.0 — direct
- pify@2.3.0 — indirect
- pinkie@2.0.4 — indirect
- pinkie-promise@2.0.1 — indirect
- promise@1.3.0 — indirect
- resolve@0.6.3 — indirect
- sliced@1.0.1 — indirect
- slide@1.1.6 — indirect
- sort-keys@1.1.2 — indirect
- strip-bom@2.0.0 — indirect
- strip-json-comments@1.0.4 — indirect
- wordwrap@0.0.3 — indirect
- wrap-sync@1.0.0 — direct
- wrappy@1.0.2 — indirect
- write-file-atomic@1.3.4 — indirect
- write-json-file@1.2.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.
| Code-Review | 0/10 — Found 0/14 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 6/10 — 8 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 6 |
| 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 | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| 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/json-future/1.1.3 — retrieved 2026-10-30T20:31:45.076Z
- https://api.deps.dev/v3/systems/npm/packages/json-future/versions/1.1.3 — retrieved 2026-10-30T20:31:45.537Z
- https://api.deps.dev/v3/systems/npm/packages/json-future/versions/1.1.3:dependencies — retrieved 2026-10-30T20:31:45.579Z
- https://api.deps.dev/v3/projects/github.com%2Fkikobeats%2Fjson-future — retrieved 2026-10-30T20:31:45.925Z