nub
Uniqueness functions
2
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
substack
Keywords
uniqueuniquniqBynubnubBy
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): nub is a 14-year-old legitimate utility by substack; edit-distance match to nuxt is a false positive for this short, semantically meaningful package name. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): nub is a 14-year-old legitimate utility by substack; edit-distance match to yup is a false positive for this short, semantically meaningful package name. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Version 0.0.0 was common in early npm packages (~2010-2012); combined with the package's age and known authorship, this is not a malicious signal. | ai |
v1.0.0
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.