@prettier/plugin-pug 2.2.0

Prettier Pug Plugin

@prettier/plugin-pug@2.2.0 was published on 2022-07-30. 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 >=14.6.0.

All @prettier/plugin-pug versions · Permanent reference to 2.2.0 · Latest release

Package specifications

Version2.2.0
License declarationMIT
Published2022-07-30T18:06:34.278Z
Node.js requirement>=14.6.0
Type declarationsNot declared
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size327.99 KiB
Published file count64
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies24
Repository stars208
Repository forks50

Install @prettier/plugin-pug 2.2.0

npm install @prettier/plugin-pug@2.2.0
pnpm add @prettier/plugin-pug@2.2.0
yarn add @prettier/plugin-pug@2.2.0

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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-Review1/10 — Found 1/7 approved changesets -- score normalized to 1
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Maintained4/10 — 5 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 4
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
License10/10 — license file detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy10/10 — security policy file detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies10/10 — all dependencies are pinned
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness