← Home

yeast

Tiny but linear growing unique id generator

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

unshift3rdeden

Keywords

yeastidgeneratorunique

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:react AI (typosquat): 'yeast' is a legitimate unique ID generator with 11+ years of history and 1.6M weekly downloads. Levenshtein proximity to 'react' is purely coincidental. ai
typosquat typosquat.levenshtein:jest AI (typosquat): 'yeast' is a legitimate unique ID generator with 11+ years of history and 1.6M weekly downloads. Levenshtein proximity to 'jest' is purely coincidental. ai
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is the genuine initial release from 2014; package has 1.6M weekly downloads and a long established history. Not a throwaway. ai
provenance publisher-changed AI (provenance): Both unshift and 3rdeden are accounts of Arnout Kazemier; legitimate account consolidation from 2015. ai
maintainer-change maintainer-added AI (maintainer-change): 3rdeden is the same author (Arnout Kazemier) consolidating npm accounts; stable for this package. ai

Versions (showing 3 of 3)

Version Deps Published
0.1.2 0 / 5
0.1.1 0 / 4
0.0.0 0 / 3

v0.1.2

2 findings
HIGH Publisher changed: unshift → 3rdeden (on 2015-09-06) provenance

This version was published by a different npm account than previous versions on 2015-09-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.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.