@glimmer/runtime 0.23.0-alpha.3

Minimal runtime needed to render Glimmer templates

@glimmer/runtime@0.23.0-alpha.3 was published on 2017-03-21. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @glimmer/runtime versions · Permanent reference to 0.23.0-alpha.3 · Latest release

Package specifications

Version0.23.0-alpha.3
License declarationMIT
Published2017-03-21T22:46:29.825Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count6
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 entrymodules/es5/index.js
Default entrycommonjs/es5/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies8
Repository stars1151
Repository forks188

Install @glimmer/runtime 0.23.0-alpha.3

npm install @glimmer/runtime@0.23.0-alpha.3
pnpm add @glimmer/runtime@0.23.0-alpha.3
yarn add @glimmer/runtime@0.23.0-alpha.3

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.

Maintained0/10 — project is archived
Code-Review7/10 — Found 11/14 approved changesets -- score normalized to 7
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness