didi 3.2.0

Dependency Injection for JavaScript

didi@3.2.0 was published on 2018-04-01. Its manifest declares 0 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 didi versions · Permanent reference to 3.2.0 · Latest release

Package specifications

Version3.2.0
License declarationMIT
Published2018-04-01T17:48:07.957Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size41.37 KiB
Published file count8
Package typeNot declared
ES module entrydist/index.esm.js
Default entrydist/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies0
Repository stars110
Repository forks17

Install didi 3.2.0

npm install didi@3.2.0
pnpm add didi@3.2.0
yarn add didi@3.2.0

Runtime dependencies

  • None declared

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.

    Code-Review0/10 — Found 0/13 approved changesets -- score normalized to 0
    Dangerous-Workflow10/10 — no dangerous workflow patterns detected
    Maintained2/10 — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
    Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
    Binary-Artifacts10/10 — no binaries found in the repo
    Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    Branch-Protection0/10 — branch protection not enabled on development/release branches
    Security-Policy10/10 — security policy file detected
    SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

    Evidence and freshness