es6-set
ECMAScript6 Set polyfill
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:event-emitter | AI (npm-metadata): Git URL points to medikoo's own repo; consistent with early-stage co-development by the same trusted author. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): es6-set is a legitimate, widely-downloaded polyfill by trusted publisher medikoo. Version 0.0.0 is an early snapshot, not a throwaway malicious package. | ai | |
| npm-metadata | url-dep:d | AI (npm-metadata): Git URL points to medikoo's own repo; consistent with early-stage co-development by the same trusted author. | ai | |
| npm-metadata | url-dep:es5-ext | AI (npm-metadata): Git URL points to medikoo's own repo; consistent with early-stage co-development by the same trusted author. | ai | |
| npm-metadata | url-dep:es6-iterator | AI (npm-metadata): Git URL points to medikoo's own repo; consistent with early-stage co-development by the same trusted author. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): The new `type` dependency is authored by medikoo (same publisher as es6-set); not a third-party injection risk. | ai | |
| dependencies | unvetted-dep:d | AI (dependencies): `d` is a long-standing medikoo-authored dependency of this package, not a new or suspicious addition. | ai | |
| dependencies | unvetted-dep:event-emitter | AI (dependencies): `event-emitter` is a long-standing medikoo-authored dependency of this package, not a new or suspicious addition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): medikoo is a long-standing trusted publisher with 103 approved packages; dormancy followed by routine maintenance update is not indicative of account takeover for this author. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.6 | 6 / 7 | |
| 0.1.5 | 5 / 3 | |
| 0.1.4 | 5 / 3 | |
| 0.1.3 | 5 / 3 | |
| 0.1.2 | 5 / 3 | |
| 0.1.1 | 5 / 3 | |
| 0.1.0 | 5 / 1 | |
| 0.0.0 | 4 / 1 |
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.