← Home

@fncts/io

2
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
publish-pattern dormant-publish AI (publish-pattern): SLSA provenance attestation confirms CI/CD publish; account takeover concern is mitigated by cryptographic attestation. ai
bogus-package bogus-package AI (bogus-package): Part of the @fncts monorepo ecosystem; low metadata signals are a known pattern for scoped library packages. ai
typosquat typosquat.levenshtein:koa AI (typosquat): @fncts/io is a scoped functional-TS library, not a typosquat of koa. ai
typosquat typosquat.levenshtein:got AI (typosquat): @fncts/io is a scoped functional-TS library, not a typosquat of got. ai
typosquat typosquat.levenshtein:pg AI (typosquat): @fncts/io is a scoped functional-TS library, not a typosquat of pg. ai
typosquat typosquat.levenshtein:qs AI (typosquat): @fncts/io is a scoped functional-TS library, not a typosquat of qs. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @fncts/io is a scoped functional-TS library, not a typosquat of joi. ai
typosquat typosquat.levenshtein:zod AI (typosquat): @fncts/io is a scoped functional-TS library, not a typosquat of zod. ai
typosquat typosquat.levenshtein:pino AI (typosquat): @fncts/io is a scoped functional-TS library, not a typosquat of pino. ai
phantom-deps phantom-dep:@fncts/transformers AI (phantom-deps): Same-scope monorepo dep; phantom-dep heuristic is a stable false positive here. ai

Versions (showing 2 of 2)

Version Deps Published
0.0.52 3 / 0
0.0.51 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

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.