react-native-paper
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): patch-package is a standard, well-known dev dependency; no arbitrary code fetch. | ai | |
| phantom-deps | phantom-dep:patch-package | AI (phantom-deps): patch-package invoked via postinstall script, not import; expected usage pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in a Babel plugin loading a configurable mappings JSON file; not arbitrary code execution. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 5.15.3 | 3 / 45 | |
| 5.15.2 | 3 / 45 | |
| 5.15.1 | 3 / 45 | |
| 5.15.0 | 3 / 45 | |
| 5.14.5 | 3 / 45 | |
| 5.14.4 | 3 / 45 | |
| 5.14.3 | 3 / 45 | |
| 5.14.2 | 3 / 45 | |
| 5.14.1 | 3 / 45 | |
| 5.14.0 | 3 / 46 | |
| 5.13.5 | 3 / 46 | |
| 5.13.4 | 3 / 46 | |
| 5.13.3 | 3 / 47 | |
| 5.13.2 | 3 / 47 | |
| 5.13.1 | 3 / 47 | |
| 5.13.0 | 4 / 47 | |
| 5.12.5 | 3 / 46 | |
| 5.12.4 | 3 / 46 | |
| 5.12.3 | 3 / 46 | |
| 5.12.2 | 3 / 46 | |
| 5.12.1 | 3 / 46 | |
| 5.12.0 | 3 / 46 | |
| 5.11.7 | 3 / 46 | |
| 5.11.6 | 3 / 46 | |
| 5.11.5 | 3 / 46 | |
| 5.11.4 | 3 / 46 | |
| 5.11.3 | 3 / 46 | |
| 5.11.2 | 3 / 46 | |
| 5.11.1 | 3 / 46 | |
| 5.11.0 | 3 / 46 | |
| 5.10.6 | 3 / 46 | |
| 5.10.5 | 3 / 46 | |
| 5.10.4 | 3 / 46 | |
| 5.10.3 | 3 / 46 | |
| 5.10.2 | 3 / 47 | |
| 5.10.1 | 3 / 47 | |
| 5.10.0 | 3 / 47 | |
| 5.9.1 | 4 / 48 | |
| 5.9.0 | 4 / 48 | |
| 5.8.0 | 3 / 48 | |
| 5.7.2 | 3 / 48 | |
| 5.7.1 | 3 / 48 | |
| 5.7.0 | 3 / 48 | |
| 5.6.0 | 3 / 48 | |
| 5.5.2 | 3 / 48 | |
| 5.5.1 | 3 / 48 | |
| 5.5.0 | 3 / 48 | |
| 5.4.1 | 3 / 48 | |
| 5.4.0 | 3 / 48 | |
| 5.3.1 | 3 / 48 | |
| 5.3.0 | 3 / 48 |
v5.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
2 findingsScript: patch-package
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
2 findingsScript: patch-package
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.