react-docgen-actual-name-handler 0.13.5

react-docgen-actual-name-handler@0.13.5 was published on 2019-02-08. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All react-docgen-actual-name-handler versions · Permanent reference to 0.13.5 · View npm registry JSON · Latest release

Package specifications

Version0.13.5
License declarationMIT
Published2019-02-08T21:03:07.971Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size5.78 KiB
Published file count5
Package typeNot declared
ES module entrydist/index.esm.js
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies23
Repository stars23566
Repository forks1398

Install react-docgen-actual-name-handler 0.13.5

npm install react-docgen-actual-name-handler@0.13.5
pnpm add react-docgen-actual-name-handler@0.13.5
yarn add react-docgen-actual-name-handler@0.13.5

Runtime dependencies

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-Review5/10 — Found 16/30 approved changesets -- score normalized to 5
Maintained0/10 — project is archived
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness