@react-native/dev-middleware
Dev server middleware for React Native
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:connect | AI (dependencies): connect is a foundational, widely-used HTTP middleware framework; legitimate dependency for a dev-server middleware package. | ai | |
| dependencies | unvetted-dep:chrome-launcher | AI (dependencies): chrome-launcher is a standard, well-known utility for launching Chrome; appropriate for React Native dev tooling. | ai | |
| dependencies | unvetted-dep:@isaacs/ttlcache | AI (dependencies): TTL cache library from npm maintainer Isaac Schlueter; widely used and legitimate. | ai | |
| dependencies | unvetted-dep:chromium-edge-launcher | AI (dependencies): Standard browser-launching utility for Edge; appropriate for React Native dev tooling. | ai | |
| dependencies | unvetted-dep:@react-native/debugger-shell | AI (dependencies): First-party React Native monorepo package at matching version 0.85.2; consistent with coordinated monorepo release. | ai | |
| dependencies | unvetted-dep:@react-native/debugger-frontend | AI (dependencies): First-party React Native monorepo package at matching version 0.85.2; consistent with coordinated monorepo release. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.85.3 | 12 / 4 | |
| 0.85.2 | 12 / 4 | |
| 0.85.1 | 12 / 4 | |
| 0.85.0 | 12 / 4 | |
| 0.84.1 | 12 / 4 | |
| 0.84.0 | 12 / 4 | |
| 0.83.9 | 12 / 4 | |
| 0.83.8 | 12 / 4 | |
| 0.83.7 | 12 / 4 | |
| 0.83.6 | 12 / 4 | |
| 0.83.5 | 12 / 4 | |
| 0.83.4 | 12 / 4 | |
| 0.83.3 | 12 / 4 | |
| 0.83.2 | 12 / 4 | |
| 0.83.1 | 12 / 4 | |
| 0.83.0 | 12 / 4 | |
| 0.82.1 | 12 / 4 | |
| 0.82.0 | 12 / 4 | |
| 0.81.6 | 11 / 3 | |
| 0.81.5 | 11 / 3 | |
| 0.81.4 | 11 / 3 | |
| 0.81.3 | 11 / 3 | |
| 0.81.2 | 11 / 3 | |
| 0.81.1 | 11 / 3 | |
| 0.81.0 | 11 / 3 | |
| 0.80.3 | 11 / 3 | |
| 0.80.2 | 11 / 3 | |
| 0.80.1 | 11 / 3 | |
| 0.80.0 | 11 / 3 | |
| 0.79.7 | 11 / 3 | |
| 0.79.6 | 11 / 3 | |
| 0.79.5 | 11 / 3 | |
| 0.79.4 | 11 / 3 | |
| 0.79.3 | 11 / 3 | |
| 0.79.2 | 11 / 3 | |
| 0.78.3 | 12 / 3 | |
| 0.77.3 | 12 / 3 |
v0.85.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.79.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.78.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.