putout 5.18.0

the pluggable code transformer

putout@5.18.0 was published on 2019-09-10. Its manifest declares 62 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.3.0.

All putout versions · Permanent reference to 5.18.0 · Latest release

Package specifications

Version5.18.0
License declarationMIT
Published2019-09-10T10:51:26.525Z
Node.js requirement>=8.3.0
Type declarationsNot declared
Runtime dependency count62
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size6570.84 KiB
Published file count46
Package typeNot declared
ES module entryNot declared
Default entrylib/putout.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars801
Repository forks45

Install putout 5.18.0

npm install putout@5.18.0
pnpm add putout@5.18.0
yarn add putout@5.18.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
SAST0/10 — no SAST tool detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness