@flaky-tests/core
Storage-agnostic core types and CLI for flaky-tests
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @flaky-tests/core; not impersonating cors — name reflects its role as the core module of the flaky-tests ecosystem. | ai | |
| semgrep | semgrep:silent-process-exec | AI (semgrep): Detached spawn used to open HTML report in browser without blocking CLI; benign and documented in source comment. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same browser-open pattern as silent-process-exec; not a reverse shell or miner. | ai |
v1.0.2
4 findingsPackage name '@flaky-tests/core' is 1 edit(s) away from popular package 'cors'.
Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/brewpirate/flaky-tests/blob/422f3698462fa834146ce2e0f75aeaaf2e69b7b6/src/cli/check.ts#L289 287 | } 288 | // Detached so we don't block the CLI while the browser loads. > 289 | const child = spawn(opener, [resolvedPath], { 290 | stdio: 'ignore', 291 | detached: true,
Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/brewpirate/flaky-tests/blob/422f3698462fa834146ce2e0f75aeaaf2e69b7b6/src/cli/check.ts#L289 287 | } 288 | // Detached so we don't block the CLI while the browser loads. > 289 | const child = spawn(opener, [resolvedPath], { 290 | stdio: 'ignore', 291 | detached: true,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.