why-did-memo-render

MITLicense declared in the package manifest.

whyDidMemoRender will give hints about what props triggered a React memo component to render

why-did-memo-render
85

Security score

0 known advisories in v1.0.16

0-100 score computed by this site from verifiable signals only: known OSV.dev advisories affecting this exact version, how recently it was published, and the repository's OpenSSF Scorecard.advisory penalty −0 · staleness penalty −15

Weekly downloads

Downloads across all versions in the last 7 days, from the official npm downloads API (api.npmjs.org).

—

Unpacked size

Size of v1.0.16 on disk after npm install extracts the tarball, as reported by the npm registry.

12.3 kB

Dependencies

Direct runtime dependencies declared by v1.0.16. Transitive dependencies are not counted here — use the lockfile audit for the full tree.

1

Last publish

When v1.0.16 was published to the registry. Long gaps can indicate an unmaintained package.

4 years ago

Security advisories

Vulnerabilities affecting v1.0.16 specifically, from OSV.dev — the open database aggregating the GitHub Advisory Database (GHSA) and CVEs. Links open the full advisory.

No known vulnerabilities affect v1.0.16.