expo-linking
Create and open deep links universally
86%
Total Score
healthy
The Expo monorepo is actively maintained, but its workflow audit is incomplete and does not explicitly name this package.
Health Score Breakdown
No build attestation or trusted-publisher identity was recorded. This limits publication transparency, but it is not by itself evidence of poor maintenance.
The repository is organization-owned, and the registry has 13 publish-capable accounts. Several accounts use outside or consumer domains, including gmail.com, jameside.com, bycedric.com, tsapeta.com, and kitten.sh; this is account hygiene caution, not evidence of a thin maintenance team.
The linked repository is a monorepo whose name does not match expo-linking, which is ordinary for a subpackage, but its README also does not mention this package; that weakens direct package-to-repository transparency.
The audit analyzed 30 of 54 workflows, so coverage is incomplete. It found high-confidence template-injection findings and high-confidence adhoc package installs, while low-confidence cache-poisoning findings carry little weight; no untrusted checkout or script-injection sink was reported, and all 136 action references were pinned.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 invariant Version ^2.2.4 | — | — |
expo-constants Version ~57.0.21 | — | — |
Weekly Downloads
Info
- Last Published
- 8 days ago
- Created
- 6 years ago
- Unpacked Size
- 0.2 MB
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.