← Home

react-native-nitro-modules

npm Repository Homepage
31
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

mrousavy

Keywords

react-nativenitroiosandroidvisionOStvOSmacOScppframeworkreactswiftnativemodulesfastjsiturboscaffoldtemplateviews

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Postinstall runs 'bun build || exit 0' — a local JS build step that gracefully no-ops if bun is absent. No network access or arbitrary code execution. Stable and benign for this package. ai

Versions (showing 31 of 31)

Version Deps Published
0.35.9 0 / 7
0.35.8 0 / 7
0.35.7 0 / 7
0.35.6 0 / 7
0.35.5 0 / 7
0.35.4 0 / 7
0.35.3 0 / 7
0.35.2 0 / 7
0.35.1 0 / 7
0.35.0 0 / 7
0.34.1 0 / 7
0.34.0 0 / 7
0.33.9 0 / 7
0.33.8 0 / 7
0.33.7 0 / 7
0.33.6 0 / 7
0.33.5 0 / 7
0.33.4 0 / 7
0.33.3 0 / 7
0.33.2 0 / 7
0.33.1 0 / 6
0.33.0 0 / 6
0.32.2 0 / 6
0.32.1 0 / 6
0.32.0 0 / 6
0.31.8 0 / 6
0.31.7 0 / 6
0.31.6 0 / 6
0.31.5 0 / 6
0.31.3 0 / 6
0.30.1 0 / 6

v0.35.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.35.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.35.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.35.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.35.5

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.

v0.35.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.35.3

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.

v0.33.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.33.0

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.

v0.32.1

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.

v0.30.1

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.