← Home

fancy-test

2
Versions
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

mdonnalleysalesforce-releasesrodespdickeyxxxrasphilco

Keywords

mocha

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Intentional test-helper pattern for setting/restoring process.env; not a secret-capture risk. ai
semgrep semgrep:dynamic-require AI (semgrep): tryRequire pattern for optional chai peer dep; stable false positive for this package. ai
phantom-deps phantom-dep:@types/chai AI (phantom-deps): @types packages are convention-loaded TypeScript type declarations, not runtime imports. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types packages are convention-loaded TypeScript type declarations, not runtime imports. ai
phantom-deps phantom-dep:@types/sinon AI (phantom-deps): @types packages are convention-loaded TypeScript type declarations, not runtime imports. ai
phantom-deps phantom-dep:@types/lodash AI (phantom-deps): @types packages are convention-loaded TypeScript type declarations, not runtime imports. ai

Versions (showing 2 of 2)

Version Deps Published
3.0.16 9 / 12
2.0.21 8 / 13

v3.0.16

2 findings
HIGH env-spread: lib/env.js:16 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/oclif/fancy-test/blob/f8fae11f3620c8da720ce0f4998f584c7356c445/lib/env.js#L16 14 | } 15 | else { > 16 | process.env = { ...process.env, ...normalizedEnv }; 17 | Object.entries(normalizedEnv) 18 | .filter(([, v]) => v === undefined)

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.

v2.0.21

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.