JsRender/JsViews 1.2.0

Best-of-breed templating in browser or on Node.js (with Express 4, Hapi and Browserify integration)

jsrender@1.2.0 was published on 2026-06-25. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All JsRender/JsViews versions · Permanent reference to 1.2.0 · Latest release

Package specifications

Version1.2.0
License declarationMIT
Published2026-06-25T23:21:16.797Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified size26.67 KiB
Minified + gzip12.36 KiB
Unpacked distribution size448.17 KiB
Published file count14
Package typeNot declared
ES module entryNot declared
Default entry./jsrender-node.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies11
Repository stars2666
Repository forks334

Install JsRender/JsViews 1.2.0

npm install jsrender@1.2.0
pnpm add jsrender@1.2.0
yarn add jsrender@1.2.0

Runtime dependencies

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.

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 1/30 approved changesets -- score normalized to 0
Maintained1/10 — 1 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 1
Binary-Artifacts10/10 — no binaries found in the repo
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
Branch-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness