expo-linking
Create and open deep links universally
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
idebrentvatneevanbaconexpoadminexponentbycedrickudochienalanhughestsapetaexpo-botphilplwschurman
Keywords
react-nativeexpoexpo-linking
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Canary/pre-release builds from the Expo monorepo CI pipeline consistently lack gitHead; this is a known artifact of their canary publish process, not a security signal. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): Expo uses date-stamped canary version numbers (e.g. X.Y.Z-canary-YYYYMMDD-commithash) as part of their documented release process; this pattern is not indicative of malicious intent for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): expo-linking is an actively developed Expo SDK package; size increases across versions are expected as features expand. Official monorepo publisher with strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer list changes are routine in large monorepo projects like Expo; no takeover indicators present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @types/qs is a type definition package for existing qs dependency; low-risk addition. | ai | |
| dependencies | unvetted-dep:@types/qs | AI (dependencies): @types/* packages are low-risk type definitions; stable for this package's TypeScript support. | ai | |
| phantom-deps | phantom-dep:@types/qs | AI (phantom-deps): Type packages are conventionally loaded; phantom status is expected and benign. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change reflects documented Expo maintainer transition; consistent with project history. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers reflect legitimate Expo project organization; consistent with publisher transition. | ai | |
| provenance | no-provenance | AI (provenance): expo-linking is an official Expo SDK package published from the expo/expo monorepo; lack of Sigstore provenance is consistent with their release process and not a risk signal. | ai |
Versions (showing 1 of 101)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 3 / 1 |