vdom 0.0.22
A DOM create and patch algorithm for vtree
vdom@0.0.22 was published on 2014-11-13. Its manifest declares 4 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 vdom versions · Permanent reference to 0.0.22 · Latest release
Package specifications
| Version | 0.0.22 |
|---|---|
| License declaration | Not declared |
| Published | 2014-11-13T04:57:35.121Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| 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 |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 87 |
| Repository forks | 18 |
Install vdom 0.0.22
npm install vdom@0.0.22 pnpm add vdom@0.0.22 yarn add vdom@0.0.22
Runtime dependencies
- global ^4.3.0
- is-object 0.1.2
- vtree 0.0.22
- x-is-array 0.1.0
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.
- dom-walk@0.1.2 — indirect
- global@4.4.0 — direct
- is-object@0.1.2 — direct
- min-document@2.19.2 — indirect
- process@0.11.10 — indirect
- vtree@0.0.22 — direct
- x-is-array@0.1.0 — direct
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 1/29 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/vdom/0.0.22 — retrieved 2026-10-29T23:30:10.449Z
- https://api.deps.dev/v3/systems/npm/packages/vdom/versions/0.0.22 — retrieved 2026-10-29T23:30:10.989Z
- https://api.deps.dev/v3/systems/npm/packages/vdom/versions/0.0.22:dependencies — retrieved 2026-10-29T23:30:11.011Z
- https://api.deps.dev/v3/projects/github.com%2FMatt-Esch%2Fvdom — retrieved 2026-10-29T23:30:11.590Z