@expo/json-file
A module for reading, writing, and manipulating JSON files
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): brentvatne is a core Expo maintainer with a long, trusted track record; transition from expo-bot automation account to named maintainer is expected and benign for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Expo monorepo package with 208 versions; lack of Sigstore provenance is a known gap for this package family, not a security signal. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 10.2.0 | 2 / 5 | |
| 10.1.1 | 2 / 5 | |
| 10.1.0 | 2 / 5 | |
| 10.0.16 | 2 / 4 | |
| 10.0.15 | 2 / 4 | |
| 10.0.14 | 2 / 4 | |
| 10.0.13 | 2 / 4 | |
| 10.0.12 | 2 / 4 | |
| 10.0.11 | 2 / 4 | |
| 10.0.10 | 2 / 4 | |
| 10.0.9 | 2 / 4 | |
| 10.0.8 | 2 / 4 | |
| 10.0.7 | 2 / 4 | |
| 10.0.6 | 2 / 4 | |
| 10.0.5 | 2 / 4 | |
| 10.0.4 | 2 / 4 | |
| 10.0.3 | 2 / 4 | |
| 10.0.2 | 2 / 4 | |
| 10.0.1 | 2 / 4 | |
| 10.0.0 | 2 / 4 | |
| 9.1.5 | 2 / 4 | |
| 9.1.4 | 2 / 4 | |
| 9.1.3 | 2 / 4 | |
| 9.1.2 | 2 / 4 | |
| 9.1.1 | 2 / 4 | |
| 9.1.0 | 2 / 4 | |
| 9.0.2 | 3 / 5 | |
| 9.0.1 | 3 / 5 | |
| 9.0.0 | 3 / 5 | |
| 8.3.3 | 3 / 4 | |
| 8.3.2 | 3 / 4 | |
| 8.3.1 | 3 / 4 | |
| 8.3.0 | 3 / 4 | |
| 8.2.37 | 3 / 3 | |
| 8.2.36 | 3 / 3 | |
| 8.2.35 | 3 / 3 | |
| 8.2.34 | 3 / 3 | |
| 8.2.33 | 3 / 3 | |
| 8.2.32 | 3 / 3 | |
| 8.2.31 | 3 / 5 | |
| 8.2.30 | 4 / 6 | |
| 8.2.29 | 4 / 6 | |
| 8.2.28 | 4 / 6 | |
| 8.2.27 | 5 / 7 | |
| 8.2.26 | 5 / 7 | |
| 8.2.25 | 5 / 7 | |
| 8.2.24 | 5 / 7 | |
| 8.2.23 | 5 / 7 | |
| 8.2.22 | 5 / 7 | |
| 8.2.21 | 5 / 7 | |
| 8.2.20 | 5 / 7 |
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v10.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.10
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.9
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-09-10. This could indicate a legitimate maintainer transition or an account compromise.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.
v10.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-08-13. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-07-03. This could indicate a legitimate maintainer transition or an account compromise.
v9.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.