js-prettify
An up-to-date version of js-beautify for Assemble's helpers.
js-prettify@1.4.0 was published on 2014-01-17. Its manifest declares 3 runtime dependencies 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 js-prettify versions · Permanent reference to 1.4.0
Package specifications
| Version | 1.4.0 |
|---|---|
| License declaration | Not declared |
| Published | 2014-01-17T00:25:58.806Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| 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 | js/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 8 |
| Repository forks | 1 |
Install js-prettify 1.4.0
npm install js-prettify@1.4.0 pnpm add js-prettify@1.4.0 yarn add js-prettify@1.4.0
Runtime dependencies
- config-chain ~1.1.5
- mkdirp 0.3.5
- nopt ~2.1.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 — direct
- ini@1.3.8 — indirect
- mkdirp@0.3.5 — direct
- nopt@2.1.2 — direct
- 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 | 0/10 — Found 0/1 approved changesets -- score normalized to 0 |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/js-prettify/1.4.0 — retrieved 2026-10-31T17:25:03.427Z
- https://api.deps.dev/v3/systems/npm/packages/js-prettify/versions/1.4.0 — retrieved 2026-10-31T17:25:04.645Z
- https://api.deps.dev/v3/systems/npm/packages/js-prettify/versions/1.4.0:dependencies — retrieved 2026-10-31T17:25:04.778Z
- https://api.deps.dev/v3/projects/github.com%2Fpsyrendust%2Fjs-prettify — retrieved 2026-10-31T17:25:05.097Z