d3-request 0.3.2
A convenient alternative to XMLHttpRequest.
d3-request@0.3.2 was published on 2016-01-29. Its manifest declares 3 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 d3-request versions · Permanent reference to 0.3.2 · Latest release
Package specifications
| Version | 0.3.2 |
|---|---|
| License declaration | BSD-3-Clause |
| Published | 2016-01-29T18:31:02.236Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| 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 | build/d3-request.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 110 |
| Repository forks | 54 |
Install d3-request 0.3.2
npm install d3-request@0.3.2 pnpm add d3-request@0.3.2 yarn add d3-request@0.3.2
Runtime dependencies
- d3-collection ~0.1.1
- d3-dispatch ~0.2.6
- d3-dsv ~0.1.14
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-collection@0.1.2 — direct
- d3-dispatch@0.2.6 — direct
- d3-dsv@0.1.14 — 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 |
|---|---|
| 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 |
| Signed-Releases | 0/10 — Project has not signed or included provenance with any releases. |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/d3-request/0.3.2 — retrieved 2026-10-29T10:00:49.053Z
- https://api.deps.dev/v3/projects/github.com%2Fd3%2Fd3-request — retrieved 2026-10-29T08:05:16.857Z
- https://api.deps.dev/v3/systems/npm/packages/d3-request/versions/0.3.2 — retrieved 2026-10-29T10:00:49.801Z
- https://api.deps.dev/v3/systems/npm/packages/d3-request/versions/0.3.2:dependencies — retrieved 2026-10-29T10:00:49.809Z