postcss 5.0.18

Tool for transforming styles with JS plugins

postcss@5.0.18 was published on 2016-02-29. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=0.12.

All postcss versions · Permanent reference to 5.0.18 · Latest release

Package specifications

Version5.0.18
License declarationMIT
Published2016-02-29T08:33:58.269Z
Node.js requirement>=0.12
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/postcss
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository stars28967
Repository forks1653

Install postcss 5.0.18

npm install postcss@5.0.18
pnpm add postcss@5.0.18
yarn add postcss@5.0.18

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-Review4/10 — Found 12/30 approved changesets -- score normalized to 4
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies10/10 — all dependencies are pinned
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing10/10 — project is fuzzed
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness