← Home

expo-glass-effect

npm Repository Homepage

A component that renders a native glass effect view on iOS.

66
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-nativeappleliquid-glassexpoexpo-glass-effect

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from expo-bot to brentvatne is a routine intra-org transition within the Expo team; both are established Expo maintainers. ai
provenance no-provenance AI (provenance): Expo SDK packages are not yet publishing with Sigstore provenance; this is informational and stable for the package. ai
dependencies unvetted-peer-dep:expo AI (dependencies): expo-glass-effect is part of the Expo SDK; peering on expo with * is the standard pattern for all Expo SDK modules. ai

Versions (showing 66 of 66)

Hide prereleases
Version Deps Published
56.0.4 0 / 7
56.0.3 0 / 7
56.0.2 0 / 7
56.0.1 0 / 6
56.0.0 0 / 6
55.0.11 0 / 5
55.0.10 0 / 5
55.0.9 0 / 5
55.0.8 0 / 5
55.0.7 0 / 5
55.0.6 0 / 5
55.0.5 0 / 5
55.0.4 0 / 5
55.0.3 0 / 5
55.0.2 0 / 5
55.0.1 0 / 5
55.0.0 0 / 5
0.1.10 0 / 5
0.1.9 0 / 5
0.1.8 0 / 5
0.1.7 0 / 5
0.1.6 0 / 5
0.1.5 0 / 5
0.1.4 0 / 5
0.1.3 0 / 5
0.1.2 0 / 5
0.1.1 0 / 5
0.1.0 0 / 5
56.0.0-canary-20260420-2ac87c0 0 / 6
56.0.0-canary-20260417-141204f 0 / 6
56.0.0-canary-20260414-e3dbafd 0 / 6
56.0.0-canary-20260409-6fc2991 0 / 6
56.0.0-canary-20260402-87c5ce2 0 / 5
56.0.0-canary-20260305-5163746 0 / 5
56.0.0-canary-20260212-4f61309 0 / 5
55.0.9-canary-20260402-9da566b 0 / 5
55.0.9-canary-20260401-5e87ef7 0 / 5
55.0.9-canary-20260328-bdc6273 0 / 5
55.0.9-canary-20260328-2049187 0 / 5
55.0.9-canary-20260327-0789fbc 0 / 5
55.0.4-canary-20260128-67ce8d5 0 / 5
55.0.0-canary-20260223-05214f1 0 / 5
0.2.0-canary-20260121-a63c0dd 0 / 5
0.2.0-canary-20260120-bb71700 0 / 5
0.2.0-canary-20260119-70f7c28 0 / 5
0.2.0-canary-20260114-d8e19f5 0 / 5
0.2.0-canary-20260113-4879b86 0 / 5
0.2.0-canary-20260113-0ce2b9c 0 / 5
0.2.0-canary-20260105-6b962e6 0 / 5
0.2.0-canary-20251230-fc48ddc 0 / 5
0.2.0-canary-20251223-b83b31e 0 / 5
0.2.0-canary-20251216-6e1f9a7 0 / 5
0.2.0-canary-20251216-3f01dbf 0 / 5
0.2.0-canary-20251212-acb11f2 0 / 5
0.2.0-canary-20251211-7da85ea 0 / 5
0.2.0-canary-20251210-1f163e3 0 / 5
0.2.0-canary-20251206-615dec1 0 / 5
0.2.0-canary-20251205-a1dedc6 0 / 5
0.2.0-canary-20251205-756eb7a 0 / 5
0.2.0-canary-20251127-587bc53 0 / 5
0.2.0-canary-20251120-e46b3cc 0 / 5
0.2.0-canary-20251119-961a032 0 / 5
0.2.0-canary-20251118-8f7ee64 0 / 5
0.2.0-canary-20251118-4ca99d5 0 / 5
0.2.0-canary-20251031-b135dff 0 / 5
0.1.9-canary-20260119-17896bf 0 / 5

v56.0.4

1 finding
INFO No provenance attestation provenance

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

v56.0.3

1 finding
INFO No provenance attestation provenance

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

v56.0.2

1 finding
INFO No provenance attestation provenance

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

v56.0.1

1 finding
INFO No provenance attestation provenance

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

v56.0.0

1 finding
INFO No provenance attestation provenance

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

v55.0.11

1 finding
INFO No provenance attestation provenance

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

v55.0.9

1 finding
LOW No provenance attestation provenance

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

v55.0.8

2 findings
HIGH Publisher changed: expo-bot → alanhughes (on 2026-03-11) provenance

This version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v55.0.7

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: expo-bot → brentvatne (on 2026-02-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.

v55.0.6

1 finding
LOW No provenance attestation provenance

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

v55.0.5

1 finding
LOW No provenance attestation provenance

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

v55.0.4

2 findings
HIGH Publisher changed: expo-bot → brentvatne (on 2026-02-03) provenance

This version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v55.0.3

1 finding
LOW No provenance attestation provenance

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

v55.0.2

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: alanhughes → brentvatne (on 2026-01-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-26. This could indicate a legitimate maintainer transition or an account compromise.

v55.0.1

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: brentvatne → alanhughes (on 2026-01-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-22. This could indicate a legitimate maintainer transition or an account compromise.

v55.0.0

2 findings
HIGH Publisher changed: expo-bot → brentvatne (on 2026-01-21) provenance

This version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.10

1 finding
INFO No provenance attestation provenance

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

v0.1.9

2 findings
HIGH Publisher changed: expo-bot → alanhughes (on 2026-02-12) provenance

This version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.8

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: expo-bot → kudochien (on 2025-12-05) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-05. This could indicate a legitimate maintainer transition or an account compromise.

v0.1.7

2 findings
HIGH Publisher changed: expo-bot → alanhughes (on 2025-11-13) provenance

This version was published by a different npm account than previous versions on 2025-11-13. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.6

2 findings
HIGH Publisher changed: expo-bot → brentvatne (on 2025-11-03) provenance

This version was published by a different npm account than previous versions on 2025-11-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.5

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.

v0.1.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.