@expo/require-utils
Reusable require and Node resolution utilities library for Expo
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:build/stacktrace.js | AI (source-diff): Source-map symbolication shim using node:module/node:url; not malicious network+exec. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Expo monorepo internal package; sparse README is normal for workspace packages. | ai | |
| provenance | publisher-changed | AI (provenance): brentvatne is a core Expo maintainer (3942 days on npm, 7952 approved packages); transition from expo-bot to named maintainer is a legitimate and expected pattern for Expo packages. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @babel/core and @babel/plugin-transform-modules-commonjs are canonical Babel packages; adding them is consistent with this package's purpose as a Node resolution/require utility. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 56.1.3 | 3 / 6 | |
| 56.1.2 | 3 / 6 | |
| 56.1.1 | 3 / 6 | |
| 56.1.0 | 3 / 6 | |
| 56.0.1 | 3 / 6 | |
| 56.0.0 | 3 / 6 | |
| 55.0.5 | 3 / 4 | |
| 55.0.4 | 3 / 4 | |
| 55.0.3 | 3 / 4 | |
| 55.0.2 | 3 / 4 | |
| 55.0.1 | 1 / 3 | |
| 55.0.0 | 1 / 3 | |
| 56.0.0-canary-20260420-2ac87c0 | 3 / 7 | |
| 56.0.0-canary-20260417-141204f | 3 / 7 | |
| 56.0.0-canary-20260414-e3dbafd | 3 / 7 | |
| 56.0.0-canary-20260409-6fc2991 | 3 / 7 | |
| 56.0.0-canary-20260402-87c5ce2 | 3 / 4 | |
| 56.0.0-canary-20260305-5163746 | 3 / 4 | |
| 56.0.0-canary-20260212-4f61309 | 1 / 3 | |
| 55.0.4-canary-20260402-9da566b | 3 / 4 | |
| 55.0.4-canary-20260401-5e87ef7 | 3 / 4 | |
| 55.0.4-canary-20260328-bdc6273 | 3 / 4 | |
| 55.0.4-canary-20260328-2049187 | 3 / 4 | |
| 55.0.4-canary-20260327-0789fbc | 3 / 4 | |
| 55.0.0-canary-20260223-05214f1 | 1 / 3 |
v56.1.3
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.1.2
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.1.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.1.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.