d3-regression 0.0.4

Calculate statistical regressions for two-dimensional data

d3-regression@0.0.4 was published on 2019-03-24. Its manifest declares 1 runtime dependency 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 d3-regression versions · Permanent reference to 0.0.4 · Latest release

Package specifications

Version0.0.4
License declarationGPL-3.0
Published2019-03-24T03:16:18.274Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9.96 KiB
Published file count11
Package typeNot declared
ES module entryindex
Default entrydist/d3-regression.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars172
Repository forks17

Install d3-regression 0.0.4

npm install d3-regression@0.0.4
pnpm add d3-regression@0.0.4
yarn add d3-regression@0.0.4

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

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.

Maintained10/10 — 23 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
Code-Review1/10 — Found 2/11 approved changesets -- score normalized to 1
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
Fuzzing0/10 — project is not fuzzed
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

Evidence and freshness