y
1
Versions
—
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
eliasgs
Keywords
inspectdebugtrace
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Single-char package name 'y' will always be flagged; not a typosquat of 'pg'. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Single-char package name 'y' will always be flagged; not a typosquat of 'qs'. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Single-char package name 'y' will always be flagged; not a typosquat of 'yup'. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 0 / 0 |
v0.3.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.