@babel/helper-transform-fixture-test-runner
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Test runner legitimately uses child_process; stable pattern across all versions of this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is part of the fixture module-loading sandbox; expected and stable for this test runner. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 10 / 1 | |
| 7.28.6 | 10 / 1 | |
| 7.28.5 | 10 / 1 | |
| 7.28.3 | 9 / 1 | |
| 7.28.0 | 9 / 1 | |
| 7.27.7 | 9 / 1 | |
| 7.27.6 | 9 / 1 |
v7.29.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.28.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.