@sentry/expo-upload-sourcemaps
CLI to upload bundles and source maps from Expo builds to Sentry.
Supply chain provenance
Status for the latest visible version.
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
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): CLI wrapper intentionally passes env vars to sentry-cli subprocess; stable pattern for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI tool that wraps sentry-cli binary via spawnSync; child_process use is expected and intentional. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.13.0 | 1 / 0 | |
| 8.12.0 | 1 / 0 | |
| 8.11.1 | 1 / 0 | |
| 8.11.0 | 1 / 0 | |
| 8.10.0 | 1 / 0 | |
| 8.9.2 | 1 / 0 | |
| 8.9.1 | 1 / 0 |
v8.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.