← Home

moo

Optimised tokenizer/lexer generator! 🐄 Much performance. Moo!

2
Versions
BSD-3-Clause
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

nfdtjvr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): moo is a well-known lexer package, not a typo of koa. ai
typosquat typosquat.levenshtein:mobx AI (typosquat): moo is a well-known lexer package, not a typo of mobx. ai
typosquat typosquat.levenshtein:got AI (typosquat): moo is a well-known lexer package, not a typo of got. ai
typosquat typosquat.levenshtein:joi AI (typosquat): moo is a well-known lexer package, not a typo of joi. ai
typosquat typosquat.levenshtein:zod AI (typosquat): moo is a well-known lexer package, not a typo of zod. ai

Versions (showing 2 of 2)

Version Deps Published
0.5.3 0 / 7
0.5.2 0 / 7

v0.5.2

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.