dagre-d3-renderer 0.4.22
A D3-based renderer for Dagre
dagre-d3-renderer@0.4.22 was published on 2017-09-06. 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 dagre-d3-renderer versions · Permanent reference to 0.4.22 · Latest release
Package specifications
| Version | 0.4.22 |
|---|---|
| License declaration | MIT |
| Published | 2017-09-06T02:55:12.754Z |
| 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 | dist/dagre-d3.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 4 |
| Repository stars | 11 |
| Repository forks | 3 |
Install dagre-d3-renderer 0.4.22
npm install dagre-d3-renderer@0.4.22 pnpm add dagre-d3-renderer@0.4.22 yarn add dagre-d3-renderer@0.4.22
Runtime dependencies
- d3 3.5.17
- dagre-layout ^0.7.8
- graphlib ^2.1.1
- lodash ^4.17.4
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.
- d3@3.5.17 — direct
- dagre-layout@0.7.10 — direct
- graphlib@2.1.8 — direct
- lodash@4.18.1 — 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.
| SAST | 0/10 — no SAST tool detected |
|---|---|
| Code-Review | 0/10 — Found 0/30 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 |
| 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/dagre-d3-renderer/0.4.22 — retrieved 2026-10-30T06:17:56.431Z
- https://api.deps.dev/v3/projects/github.com%2Ftylingsoft%2Fdagre-d3-renderer — retrieved 2026-10-30T05:49:01.834Z
- https://api.deps.dev/v3/systems/npm/packages/dagre-d3-renderer/versions/0.4.22 — retrieved 2026-10-30T06:17:56.930Z
- https://api.deps.dev/v3/systems/npm/packages/dagre-d3-renderer/versions/0.4.22:dependencies — retrieved 2026-10-30T06:17:56.957Z