@sentry/react-native
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): env-spread in sentry-cli invocation script is intentional; passes env vars to CLI tool. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in build/upload script to invoke sentry-cli; expected for this package. | ai | |
| phantom-deps | phantom-dep:@sentry/cli | AI (phantom-deps): Same-org dep used as a CLI tool in build scripts; not directly imported in JS but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@sentry/types | AI (phantom-deps): Types-only package; not imported at runtime but legitimately declared as a dependency. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 8.18.0 | 6 / 38 | |
| 8.17.2 | 6 / 38 | |
| 8.17.1 | 6 / 38 | |
| 8.17.0 | 6 / 38 | |
| 8.16.0 | 6 / 38 | |
| 8.15.1 | 6 / 37 | |
| 8.15.0 | 6 / 37 | |
| 8.14.2 | 6 / 37 | |
| 8.14.1 | 6 / 37 | |
| 8.14.0 | 6 / 37 | |
| 8.13.0 | 6 / 37 | |
| 8.12.0 | 7 / 37 | |
| 8.11.1 | 7 / 37 | |
| 8.11.0 | 7 / 37 | |
| 8.10.0 | 7 / 36 | |
| 8.9.2 | 7 / 38 | |
| 8.9.1 | 7 / 38 | |
| 8.9.0 | 7 / 38 | |
| 8.8.0 | 6 / 38 | |
| 8.7.0 | 6 / 38 | |
| 8.6.0 | 6 / 42 | |
| 8.5.0 | 6 / 42 | |
| 8.4.0 | 6 / 42 | |
| 8.3.0 | 6 / 42 | |
| 8.2.0 | 6 / 42 | |
| 8.1.0 | 6 / 42 | |
| 8.0.0 | 6 / 42 | |
| 7.13.0 | 6 / 42 | |
| 7.12.1 | 6 / 42 | |
| 7.12.0 | 6 / 42 | |
| 7.11.0 | 6 / 42 | |
| 7.10.0 | 6 / 42 | |
| 7.9.0 | 6 / 42 | |
| 7.8.0 | 6 / 42 | |
| 7.7.0 | 6 / 42 | |
| 7.6.0 | 6 / 42 | |
| 7.5.0 | 6 / 42 |
v8.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.