← Home

hat

npm Repository

generate random IDs and avoid collisions

4
Versions
MIT/X11
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

iduiduuidrandomhatrackunique

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): 'hat' is a legitimate, intentional package name by substack, 14+ years old with 300k weekly downloads. Not a typosquat of hapi. ai
typosquat typosquat.levenshtein:got AI (typosquat): 'hat' is a legitimate, intentional package name by substack, 14+ years old with 300k weekly downloads. Not a typosquat of got. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Version 0.0.0 is the genuine initial release of this 14-year-old package by substack. Not indicative of malicious intent. ai

Versions (showing 4 of 4)

Version Deps Published
0.0.3 0 / 1
0.0.2 0 / 1
0.0.1 0 / 1
0.0.0 0 / 1

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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

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.