← Home

@sentry/react-native

npm Repository Homepage
10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sentry-bot

Keywords

react-nativesentrycrashreportingios

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 10 of 10)

Version Deps Published
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

v8.13.0

1 finding
LOW No provenance attestation provenance

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

v8.12.0

1 finding
LOW No provenance attestation provenance

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

v8.11.1

1 finding
LOW No provenance attestation provenance

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

v8.11.0

1 finding
LOW No provenance attestation provenance

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

v8.10.0

1 finding
LOW No provenance attestation provenance

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

v8.9.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.

v8.9.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.

v8.8.0

2 findings
HIGH env-spread: scripts/expo-upload-sourcemaps.js:284 semgrep

Spreading entire process.env into an object — may capture all secrets 282 | 283 | const result = spawnSync(sentryCliBin, args, { > 284 | env: { 285 | ...process.env, 286 | [SENTRY_PROJECT]: sentryProject,

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.

v8.7.0

2 findings
HIGH env-spread: scripts/expo-upload-sourcemaps.js:231 semgrep

Spreading entire process.env into an object — may capture all secrets 229 | 230 | const result = spawnSync(sentryCliBin, args, { > 231 | env: { 232 | ...process.env, 233 | [SENTRY_PROJECT]: sentryProject,

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.