expo-test-runner
Script that enchants test experience.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on a config-file reader pattern; stable and intentional for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a runtime dep declared in dependencies; phantom-dep is a false positive here. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 8 / 5 | |
| 0.4.0 | 8 / 5 | |
| 0.3.15 | 8 / 6 | |
| 0.3.14 | 8 / 5 | |
| 0.3.13 | 8 / 5 | |
| 0.3.12 | 8 / 6 | |
| 0.3.11 | 8 / 6 | |
| 0.3.10 | 8 / 6 | |
| 0.3.9 | 8 / 6 | |
| 0.3.8 | 8 / 6 | |
| 0.3.7 | 8 / 6 | |
| 0.3.6 | 8 / 6 | |
| 0.3.5 | 8 / 6 | |
| 0.3.4 | 8 / 6 | |
| 0.3.3 | 8 / 6 | |
| 0.3.2 | 8 / 6 | |
| 0.3.1 | 8 / 6 | |
| 0.3.0 | 8 / 6 | |
| 0.2.5 | 8 / 6 | |
| 0.2.4 | 8 / 6 | |
| 0.2.3 | 8 / 6 | |
| 0.2.2 | 8 / 6 | |
| 0.2.1 | 8 / 6 | |
| 0.2.0 | 8 / 6 | |
| 0.1.1 | 9 / 7 | |
| 0.1.0 | 9 / 7 |
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.