react-docgen-displayname-handler 2.0.0

A handler for react-docgen that tries to infer the displayName of a component

react-docgen-displayname-handler@2.0.0 was published on 2018-06-06. Its manifest declares 0 runtime dependencies and 2 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=4.

All react-docgen-displayname-handler versions · Permanent reference to 2.0.0 · Latest release

Package specifications

Version2.0.0
License declarationMIT
Published2018-06-06T08:53:07.190Z
Node.js requirement>=4
Type declarationsNot declared
Runtime dependency count0
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9.59 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entrydistribution/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars8
Repository forks4

Install react-docgen-displayname-handler 2.0.0

npm install react-docgen-displayname-handler@2.0.0
pnpm add react-docgen-displayname-handler@2.0.0
yarn add react-docgen-displayname-handler@2.0.0

Runtime dependencies

  • None declared

Peer requirements

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/17 approved changesets -- score normalized to 0
    Binary-Artifacts10/10 — no binaries found in the repo
    Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
    CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
    Security-Policy0/10 — security policy file not detected
    Fuzzing0/10 — project is not fuzzed
    License10/10 — license file detected
    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