react-native-nitro-modules
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Early-version growth of a legitimate scaffold project, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected growth for a 0.0.x package under active development. | ai | |
| 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 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.36.1 | 0 / 8 | |
| 0.36.0 | 0 / 8 | |
| 0.35.10 | 0 / 8 | |
| 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 | |
| 0.1.6 | 0 / 14 | |
| 0.0.6 | 0 / 15 | |
| 0.0.2 | 0 / 16 |
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.