← Home

@fncts/test

npm Repository
4
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

0x706b

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is superseded by stronger CI/CD integrity signal. ai
publish-pattern dormant-publish AI (publish-pattern): Publisher has clean track record and SLSA attestation confirms legitimate CI/CD publish; dormancy likely reflects development cadence. ai
typosquat typosquat.levenshtein:jest AI (typosquat): @fncts/test is a scoped test utility in the @fncts ecosystem, not a typosquat of jest. ai
typosquat typosquat.levenshtein:next AI (typosquat): @fncts/test is a scoped test utility in the @fncts ecosystem, not a typosquat of next. ai
typosquat typosquat.levenshtein:vitest AI (typosquat): @fncts/test wraps vitest as a peer dep; it is not a typosquat of vitest. ai
phantom-deps phantom-dep:@fncts/typelevel AI (phantom-deps): @fncts/typelevel is a type-level utility in the same org scope; likely used only at type level, not imported at runtime. ai

Versions (showing 4 of 4)

Version Deps Published
0.0.52 3 / 0
0.0.51 3 / 0
0.0.50 3 / 0
0.0.49 3 / 0

v0.0.52

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 0x706b.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.51

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'jest' typosquat

Package name '@fncts/test' is 1 edit(s) away from popular package 'jest'.

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.

v0.0.50

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.

v0.0.49

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.