@putout/processor-json 2.1.3
putout processor adds ability to lint json
@putout/processor-json@2.1.3 was published on 2021-03-18. Its manifest declares 1 runtime dependency and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=12.
All @putout/processor-json versions · Permanent reference to 2.1.3 · Latest release
Package specifications
| Version | 2.1.3 |
|---|---|
| License declaration | MIT |
| Published | 2021-03-18T15:18:31.864Z |
| Node.js requirement | >=12 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 3.61 KiB |
| Published file count | 4 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/json.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 1 |
| Repository stars | 801 |
| Repository forks | 45 |
Install @putout/processor-json 2.1.3
npm install @putout/processor-json@2.1.3 pnpm add @putout/processor-json@2.1.3 yarn add @putout/processor-json@2.1.3
Runtime dependencies
- remove-blank-lines ^1.4.1
Peer requirements
- putout >=11
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- remove-blank-lines@1.4.2 — 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/30 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
| License | 10/10 — license file detected |
| SAST | 0/10 — no SAST tool detected |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Fuzzing | 0/10 — project is not fuzzed |
Evidence and freshness
- https://registry.npmjs.org/%40putout%2Fprocessor-json/2.1.3 — retrieved 2026-10-30T08:07:41.726Z
- https://api.deps.dev/v3/systems/npm/packages/%40putout%2Fprocessor-json/versions/2.1.3:dependencies — retrieved 2026-10-30T08:07:42.320Z
- https://api.deps.dev/v3/systems/npm/packages/%40putout%2Fprocessor-json/versions/2.1.3 — retrieved 2026-10-30T08:07:42.224Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/projects/github.com%2Fcoderaiser%2Fputout — retrieved 2026-10-30T07:32:47.709Z