← Home

set

npm Repository Homepage

An implementation of Sets in JavaScript

4
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

gkatsev

Keywords

setintersectuniondifference

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:next AI (typosquat): 'set' is a generic data structure name, 15+ years old, predating 'next'. 2-edit distance from a 3-char word is coincidental, not impersonation. ai
typosquat typosquat.levenshtein:jest AI (typosquat): 'set' is a generic data structure name, 15+ years old, predating 'jest'. 2-edit distance from a 3-char word is coincidental, not impersonation. ai
typosquat typosquat.levenshtein:got AI (typosquat): 'set' is a generic data structure name, 15+ years old, predating 'got'. 2-edit distance from a 3-char word is coincidental, not impersonation. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.1 0 / 1
1.1.0 0 / 1
1.0.1 0 / 1
1.0.0 0 / 0

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.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.

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

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