pretty 0.1.2
Some tweaks for beautifying HTML with js-beautify according to my preferences.
pretty@0.1.2 was published on 2013-12-29. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All pretty versions · Permanent reference to 0.1.2 · Latest release
Package specifications
| Version | 0.1.2 |
|---|---|
| License declaration | Not declared |
| Published | 2013-12-29T09:09:43.931Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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 | 7 |
| Repository stars | 138 |
| Repository forks | 17 |
Install pretty 0.1.2
npm install pretty@0.1.2 pnpm add pretty@0.1.2 yarn add pretty@0.1.2
Runtime dependencies
- js-beautify ~1.4.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.
- abbrev@1.1.1 — indirect
- config-chain@1.1.13 — indirect
- ini@1.3.8 — indirect
- js-beautify@1.4.2 — direct
- mkdirp@0.3.5 — indirect
- nopt@2.1.2 — indirect
- proto-list@1.2.4 — indirect
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 | 1/10 — Found 2/18 approved changesets -- score normalized to 1 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | 0/10 — security policy file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/pretty/0.1.2 — retrieved 2026-10-29T13:18:12.664Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fpretty — retrieved 2026-10-29T10:02:54.705Z
- https://api.deps.dev/v3/systems/npm/packages/pretty/versions/0.1.2 — retrieved 2026-10-29T13:18:13.215Z
- https://api.deps.dev/v3/systems/npm/packages/pretty/versions/0.1.2:dependencies — retrieved 2026-10-29T13:18:13.234Z