← Home

react-native-restart

npm Repository Homepage
2
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

avishayil

Keywords

react-nativeiosandroid

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Moved to GitHub Actions CI/CD publishing with SLSA provenance from the same repo. ai
publish-pattern dormant-publish AI (publish-pattern): Mature RN native module; infrequent updates are normal; provenance confirms legitimate origin. ai

Versions (showing 2 of 2)

Version Deps Published
0.0.28 0 / 23
0.0.27 0 / 20

v0.0.28

2 findings
HIGH Publisher changed: avishayil → GitHub Actions (on 2026-05-28) provenance

This version was published by a different npm account than previous versions on 2026-05-28. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.