← Home

expo-status-bar

npm Repository Homepage

Provides the same interface as the React Native StatusBar API, but with slightly different defaults to work great in Expo environments.

99
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-status-bar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): brentvatne is a known Expo core team member; transition from expo-bot (automated) to a named maintainer is a legitimate and expected pattern for the Expo monorepo. ai

Versions (showing 99 of 99)

Hide prereleases
Version Deps Published
56.0.4 0 / 8
56.0.3 0 / 8
56.0.2 0 / 8
56.0.1 0 / 7
56.0.0 0 / 7
55.0.6 1 / 5
55.0.5 1 / 5
55.0.4 1 / 5
55.0.3 1 / 5
55.0.2 1 / 5
55.0.1 1 / 5
55.0.0 1 / 5
3.0.9 1 / 5
3.0.8 1 / 5
3.0.7 1 / 5
3.0.6 1 / 5
3.0.5 1 / 5
3.0.4 1 / 5
3.0.3 1 / 5
3.0.2 2 / 5
3.0.1 2 / 5
3.0.0 2 / 4
2.2.3 2 / 4
2.2.2 2 / 4
2.2.1 2 / 4
2.2.0 2 / 4
2.1.0 1 / 4
2.0.1 0 / 4
2.0.0 0 / 4
1.12.1 0 / 4
1.12.0 0 / 4
1.11.1 0 / 4
1.11.0 0 / 4
1.10.0 0 / 4
1.9.0 0 / 4
1.8.0 0 / 4
1.7.1 0 / 4
1.7.0 0 / 4
1.6.0 0 / 4
1.5.0 0 / 4
1.4.4 0 / 4
1.4.3 0 / 4
1.4.2 0 / 4
1.4.1 0 / 1
1.4.0 0 / 1
1.3.0 0 / 1
1.2.0 0 / 1
1.1.0 0 / 1
1.0.4 0 / 1
1.0.3 0 / 1
1.0.2 0 / 1
1.0.0 0 / 1
0.2.1 0 / 1
0.2.0 0 / 1
0.1.6 1 / 1
0.1.5 1 / 1
0.1.4 1 / 1
0.1.3 1 / 1
0.1.2 1 / 1
0.1.1 1 / 1
0.1.0 0 / 1
56.0.0-canary-20260420-2ac87c0 0 / 7
56.0.0-canary-20260417-141204f 0 / 7
56.0.0-canary-20260414-e3dbafd 0 / 7
56.0.0-canary-20260409-6fc2991 0 / 7
56.0.0-canary-20260402-87c5ce2 1 / 5
56.0.0-canary-20260305-5163746 1 / 5
56.0.0-canary-20260212-4f61309 1 / 5
55.0.5-canary-20260402-9da566b 1 / 5
55.0.5-canary-20260401-5e87ef7 1 / 5
55.0.5-canary-20260328-bdc6273 1 / 5
55.0.5-canary-20260328-2049187 1 / 5
55.0.5-canary-20260327-0789fbc 1 / 5
55.0.3-canary-20260128-67ce8d5 1 / 5
55.0.0-canary-20260223-05214f1 1 / 5
3.0.10-canary-20260121-a63c0dd 1 / 5
3.0.10-canary-20260120-bb71700 1 / 5
3.0.10-canary-20260119-70f7c28 1 / 5
3.0.10-canary-20260119-17896bf 1 / 5
3.0.10-canary-20260114-d8e19f5 1 / 5
3.0.10-canary-20260113-4879b86 1 / 5
3.0.10-canary-20260113-0ce2b9c 1 / 5
3.0.10-canary-20260105-6b962e6 1 / 5
3.0.10-canary-20251230-fc48ddc 1 / 5
3.0.10-canary-20251223-b83b31e 1 / 5
3.0.10-canary-20251216-6e1f9a7 1 / 5
3.0.10-canary-20251216-3f01dbf 1 / 5
3.0.10-canary-20251212-acb11f2 1 / 5
3.0.10-canary-20251211-7da85ea 1 / 5
3.0.10-canary-20251210-1f163e3 1 / 5
3.0.10-canary-20251206-615dec1 1 / 5
3.0.10-canary-20251205-a1dedc6 1 / 5
3.0.10-canary-20251205-756eb7a 1 / 5
3.0.9-canary-20251127-587bc53 1 / 5
3.0.9-canary-20251120-e46b3cc 1 / 5
3.0.9-canary-20251119-961a032 1 / 5
3.0.9-canary-20251118-8f7ee64 1 / 5
3.0.9-canary-20251118-4ca99d5 1 / 5
3.0.9-canary-20251031-b135dff 1 / 5

v56.0.4

1 finding
LOW No provenance attestation provenance

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

v56.0.3

1 finding
LOW No provenance attestation provenance

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

v56.0.2

1 finding
LOW No provenance attestation provenance

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

v56.0.1

1 finding
LOW No provenance attestation provenance

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

v56.0.0

1 finding
LOW No provenance attestation provenance

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

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
LOW No provenance attestation provenance

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.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: expo-bot → alanhughes (on 2026-02-16) provenance

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

v55.0.2

2 findings
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

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.

v3.0.9

2 findings
LOW No provenance attestation provenance

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.

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: brentvatne → alanhughes (on 2025-08-25) provenance

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

v3.0.3

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.

v3.0.2

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.

v3.0.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.

v3.0.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.

v2.2.3

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.

v2.2.2

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.

v2.2.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.

v2.2.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.

v2.1.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.

v2.0.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.

v2.0.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.

v1.12.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.