use-callback-ref 1.3.3

The same useRef, but with callback

use-callback-ref@1.3.3 was published on 2024-12-17. Its manifest declares 1 runtime dependency and 2 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=10.

All use-callback-ref versions · Permanent reference to 1.3.3 · Latest release

Package specifications

Version1.3.3
License declarationMIT
Published2024-12-17T11:07:58.012Z
Node.js requirement>=10
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size50.60 KiB
Published file count63
Package typeNot declared
ES module entrydist/es2015/index.js
Default entrydist/es5/index.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies1
Repository stars309
Repository forks7

Install use-callback-ref 1.3.3

npm install use-callback-ref@1.3.3
pnpm add use-callback-ref@1.3.3
yarn add use-callback-ref@1.3.3

Runtime dependencies

Peer requirements

  • @types/react * (optional peer)
  • react ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 || ^19.0.0-rc

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-Review1/10 — Found 3/24 approved changesets -- score normalized to 1
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