@expo/config-types MIT 51 versions

@expo/config-types

npm Repository Homepage

Types for the Expo config object app.config.ts

51

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

jsonapp.jsonapp.config.jsreact-nativeexporeact

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): alanhughes is a known Expo maintainer with strong track record (5824 approved). The expo-bot → human publisher pattern is consistent with legitimate manual releases in the Expo ecosystem.	ai	2026/04/23

Versions (showing 51 of 87)

Show 35 prereleases View all versions

Version	Deps	Published
56.0.5	0 / 6	2026-05-20
56.0.4	0 / 6	2026-05-14
56.0.3	0 / 6	2026-05-13
56.0.2	0 / 5	2026-05-08
56.0.1	0 / 5	2026-05-06
56.0.0	0 / 5	2026-05-05
55.0.5	0 / 2	2026-02-25
55.0.4	0 / 2	2026-02-03
55.0.3	0 / 2	2026-01-26
55.0.2	0 / 2	2026-01-22
55.0.1	0 / 2	2026-01-22
55.0.0	0 / 2	2026-01-21
54.0.10	0 / 2	2025-12-11
54.0.9	0 / 2	2025-12-04
54.0.8	0 / 2	2025-09-11
54.0.7	0 / 2	2025-09-02
54.0.6	0 / 2	2025-08-31
54.0.5	0 / 2	2025-08-27
54.0.4	0 / 2	2025-08-21
54.0.3	0 / 2	2025-08-18
54.0.2	0 / 2	2025-08-17
54.0.1	0 / 2	2025-08-15
54.0.0	0 / 2	2025-08-13
53.0.5	0 / 2	2025-07-03
53.0.4	0 / 2	2025-05-06
53.0.3	0 / 2	2025-04-30
53.0.2	0 / 2	2025-04-30
53.0.1	0 / 2	2025-04-28
53.0.0	0 / 2	2025-04-25
52.0.5	0 / 3	2025-02-21
52.0.4	0 / 3	2025-02-06
52.0.3	0 / 3	2025-01-10
52.0.2	0 / 3	2025-01-07
52.0.1	0 / 3	2024-11-13
52.0.0	0 / 3	2024-11-11
51.0.3	0 / 3	2024-09-24
51.0.2	0 / 3	2024-06-28
51.0.1	0 / 3	2024-06-10
51.0.0	0 / 3	2024-04-18
50.0.1	0 / 3	2024-04-15
50.0.0	0 / 3	2023-12-12
49.0.0	0 / 3	2023-06-21
48.0.0	0 / 2	2023-02-03
47.0.0	0 / 2	2022-10-25
46.0.2	0 / 2	2022-08-11
46.0.1	0 / 2	2022-07-18
46.0.0	0 / 2	2022-07-07
45.0.0	0 / 1	2022-04-27
44.0.0	0 / 1	2022-02-10
43.0.1	0 / 1	2021-10-22
43.0.0	0 / 1	2021-10-05

v56.0.5

1 finding

LOW No provenance attestation provenance

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

v56.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: alanhughes → brentvatne (on 2026-05-14) provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v55.0.1

1 finding

LOW No provenance attestation provenance

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

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.

v54.0.10

2 findings

HIGH Publisher changed: expo-bot → alanhughes (on 2025-12-11) provenance

This version was published by a different npm account than previous versions on 2025-12-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.

v54.0.9

2 findings

HIGH Publisher changed: expo-bot → kudochien (on 2025-12-04) provenance

This version was published by a different npm account than previous versions on 2025-12-04. 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.

v54.0.8

1 finding

LOW No provenance attestation provenance

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

v54.0.7

1 finding

LOW No provenance attestation provenance

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

v54.0.6

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-31) provenance

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

v54.0.5

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-27) provenance

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

v54.0.4

1 finding

LOW No provenance attestation provenance

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

v54.0.3

1 finding

LOW No provenance attestation provenance

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

v54.0.2

1 finding

LOW No provenance attestation provenance

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

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

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

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

v53.0.4

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.

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

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

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

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

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

v52.0.4

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.

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

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

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

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

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

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

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