← Home

react-native-nitro-image

npm Repository Homepage

A superfast in-memory Image type and view component for React Native, built with Nitro!

13
Versions
MIT
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-nativenitro

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): mrousavy is a prolific RN ecosystem author; templated names and sparse README are normal for this package family. ai
install-scripts install-script:postinstall AI (install-scripts): postinstall runs `tsc || exit 0` — benign TypeScript type-check, no network or shell exec risk. ai

Versions (showing 13 of 13)

Version Deps Published
0.15.1 0 / 6
0.15.0 0 / 6
0.14.0 0 / 6
0.13.1 0 / 6
0.13.0 0 / 6
0.12.0 0 / 6
0.11.1 0 / 6
0.11.0 0 / 6
0.10.2 0 / 7
0.10.1 0 / 7
0.8.2 0 / 7
0.3.2 0 / 13
0.2.0 0 / 13

v0.15.1

1 finding
LOW No provenance attestation provenance

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

v0.15.0

1 finding
LOW No provenance attestation provenance

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

v0.13.1

1 finding
LOW No provenance attestation provenance

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

v0.13.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.12.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.11.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.11.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.10.1

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: tsc || exit 0;

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.8.2

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: tsc || exit 0;

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.3.2

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.2.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.