@expo/require-utils 58.0.5

Reusable require and Node resolution utilities library for Expo

@expo/require-utils@58.0.5 was published on 2026-10-28. Its manifest declares 3 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @expo/require-utils versions · Permanent reference to 58.0.5 · Latest release

Package specifications

Version58.0.5
License declarationMIT
Published2026-10-28T15:29:47.745Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size81.43 KiB
Published file count27
Package typeNot declared
ES module entryNot declared
Default entry./build/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependenciesUnknown
Repository stars52895
Repository forks14690

Install @expo/require-utils 58.0.5

npm install @expo/require-utils@58.0.5
pnpm add @expo/require-utils@58.0.5
yarn add @expo/require-utils@58.0.5

Runtime dependencies

Peer requirements

  • typescript ^5.0.0 || ^5.0.0-0 || ^6.0.0 || ^7.0.0 (optional peer)

Optional dependencies

  • None declared

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.

Maintained10/10 — 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Code-Review9/10 — Found 29/30 approved changesets -- score normalized to 9
Security-Policy4/10 — security policy file detected
License10/10 — license file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts0/10 — binaries present in source code
Pinned-Dependencies9/10 — dependency not pinned by hash detected -- score normalized to 9
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness