← Home

ow

npm Repository Homepage

Function argument validation for humans

3
Versions
MIT
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

sindresorhus

Keywords

typetypescheckcheckingguardguardsassertassertionpredicatepredicatesisvalidatevalidationutilityutiltypeofinstanceofobject

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): ow is a legitimate 2-char package by sindresorhus; short names trivially match Levenshtein distance 2 — not a typosquat. ai
typosquat typosquat.levenshtein:got AI (typosquat): ow is a legitimate 2-char package by sindresorhus; short names trivially match Levenshtein distance 2 — not a typosquat. ai
typosquat typosquat.levenshtein:pg AI (typosquat): ow is a legitimate 2-char package by sindresorhus; short names trivially match Levenshtein distance 2 — not a typosquat. ai
typosquat typosquat.levenshtein:qs AI (typosquat): ow is a legitimate 2-char package by sindresorhus; short names trivially match Levenshtein distance 2 — not a typosquat. ai
typosquat typosquat.levenshtein:joi AI (typosquat): ow is a legitimate 2-char package by sindresorhus; short names trivially match Levenshtein distance 2 — not a typosquat. ai
typosquat typosquat.levenshtein:zod AI (typosquat): ow is a legitimate 2-char package by sindresorhus; short names trivially match Levenshtein distance 2 — not a typosquat. ai

Versions (showing 3 of 3)

Version Deps Published
3.1.1 6 / 11
3.1.0 6 / 11
3.0.0 6 / 11

v3.1.1

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.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

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.