@eslint/js MIT 51 versions

@eslint/js

npm Repository Homepage

ESLint JavaScript language implementation

51

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

openjsfoundationeslintbot

Keywords

javascripteslint-plugineslint

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:qs	AI (typosquat): @eslint/js is the official ESLint JS package under the @eslint org scope; Levenshtein comparison to 'qs' is a false positive driven by the short 'js' suffix.	ai	2026/04/24
typosquat	typosquat.levenshtein:jest	AI (typosquat): @eslint/js is the official ESLint JS package; no relation to 'jest'. False positive from short suffix comparison.	ai	2026/04/24
typosquat	typosquat.levenshtein:pg	AI (typosquat): @eslint/js is the official ESLint JS package; no relation to 'pg'. False positive from short suffix comparison.	ai	2026/04/24
typosquat	typosquat.levenshtein:rxjs	AI (typosquat): @eslint/js is the official ESLint JS package; no relation to 'rxjs'. False positive from short suffix comparison.	ai	2026/04/24
typosquat	typosquat.levenshtein:joi	AI (typosquat): @eslint/js is the official ESLint JS package; no relation to 'joi'. False positive from short suffix comparison.	ai	2026/04/24
typosquat	typosquat.levenshtein:ajv	AI (typosquat): @eslint/js is the official ESLint JS package; no relation to 'ajv'. False positive from short suffix comparison.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Legitimate official ESLint package; lack of provenance is common and not a risk signal for this well-established publisher.	ai	2026/04/24

Versions (showing 51 of 80)

Hide prereleases View all versions

Version	Deps	Published
10.0.1	0 / 0	2026-02-06
10.0.0	0 / 0	2024-07-26
9.39.4	0 / 0	2026-03-06
9.39.3	0 / 0	2026-02-20
9.39.2	0 / 0	2025-12-12
9.39.1	0 / 0	2025-11-03
9.39.0	0 / 0	2025-10-31
9.38.0	0 / 0	2025-10-17
9.37.0	0 / 0	2025-10-03
9.36.0	0 / 0	2025-09-19
9.35.0	0 / 0	2025-09-05
9.34.0	0 / 0	2025-08-22
9.33.0	0 / 0	2025-08-08
9.32.0	0 / 0	2025-07-25
9.31.0	0 / 0	2025-07-11
9.30.1	0 / 0	2025-07-01
9.30.0	0 / 0	2025-06-27
9.29.0	0 / 0	2025-06-13
9.28.0	0 / 0	2025-05-30
9.27.0	0 / 0	2025-05-16
9.26.0	0 / 0	2025-05-02
9.25.1	0 / 0	2025-04-21
9.25.0	0 / 0	2025-04-18
9.24.0	0 / 0	2025-04-04
9.23.0	0 / 0	2025-03-21
9.22.0	0 / 0	2025-03-07
9.21.0	0 / 0	2025-02-21
9.20.0	0 / 0	2025-02-07
9.19.0	0 / 0	2025-01-24
9.18.0	0 / 0	2025-01-10
9.17.0	0 / 0	2024-12-13
9.16.0	0 / 0	2024-11-29
9.15.0	0 / 0	2024-11-15
9.14.0	0 / 0	2024-11-01
9.13.0	0 / 0	2024-10-18
9.12.0	0 / 0	2024-10-04
9.11.1	0 / 0	2024-09-23
9.11.0	0 / 0	2024-09-20
9.10.0	0 / 0	2024-09-06
9.9.1	0 / 0	2024-08-23
9.9.0	0 / 0	2024-08-09
9.8.0	0 / 0	2024-07-26
9.7.0	0 / 0	2024-07-12
9.6.0	0 / 0	2024-06-28
9.5.0	0 / 0	2024-06-14
9.4.0	0 / 0	2024-05-31
9.3.0	0 / 0	2024-05-17
9.2.0	0 / 0	2024-05-03
9.1.1	0 / 0	2024-04-19
9.1.0	0 / 0	2024-04-19
9.0.0	0 / 0	2024-04-05

v10.0.1

1 finding

LOW No provenance attestation provenance

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

v10.0.0

1 finding

LOW No provenance attestation provenance

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

v9.39.4

1 finding

LOW No provenance attestation provenance

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

v9.39.3

1 finding

LOW No provenance attestation provenance

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

v9.39.2

1 finding

LOW No provenance attestation provenance

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

v9.39.1

1 finding

LOW No provenance attestation provenance

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

v9.39.0

1 finding

LOW No provenance attestation provenance

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

v9.38.0

1 finding

LOW No provenance attestation provenance

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

v9.37.0

1 finding

LOW No provenance attestation provenance

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

v9.36.0

1 finding

LOW No provenance attestation provenance

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

v9.35.0

1 finding

LOW No provenance attestation provenance

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

v9.34.0

1 finding

LOW No provenance attestation provenance

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

v9.33.0

1 finding

LOW No provenance attestation provenance

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

v9.32.0

1 finding

LOW No provenance attestation provenance

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

v9.31.0

1 finding

LOW No provenance attestation provenance

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

v9.30.1

1 finding

LOW No provenance attestation provenance

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

v9.30.0

1 finding

LOW No provenance attestation provenance

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

v9.29.0

1 finding

LOW No provenance attestation provenance

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

v9.28.0

1 finding

LOW No provenance attestation provenance

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

v9.27.0

1 finding

LOW No provenance attestation provenance

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

v9.26.0

1 finding

LOW No provenance attestation provenance

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

v9.25.1

1 finding

LOW No provenance attestation provenance

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

v9.25.0

1 finding

LOW No provenance attestation provenance

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

v9.24.0

1 finding

LOW No provenance attestation provenance

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

v9.23.0

1 finding

LOW No provenance attestation provenance

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

v9.22.0

1 finding

LOW No provenance attestation provenance

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

v9.21.0

1 finding

LOW No provenance attestation provenance

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

v9.20.0

1 finding

LOW No provenance attestation provenance

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

v9.19.0

1 finding

LOW No provenance attestation provenance

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

v9.18.0

1 finding

LOW No provenance attestation provenance

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

v9.17.0

1 finding

LOW No provenance attestation provenance

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

v9.16.0

1 finding

LOW No provenance attestation provenance

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

v9.15.0

1 finding

LOW No provenance attestation provenance

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

v9.14.0

1 finding

LOW No provenance attestation provenance

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

v9.13.0

1 finding

LOW No provenance attestation provenance

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

v9.12.0

1 finding

LOW No provenance attestation provenance

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

v9.11.1

1 finding

LOW No provenance attestation provenance

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

v9.11.0

1 finding

LOW No provenance attestation provenance

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

v9.10.0

1 finding

LOW No provenance attestation provenance

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

v9.9.1

1 finding

LOW No provenance attestation provenance

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

v9.9.0

1 finding

LOW No provenance attestation provenance

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

v9.8.0

1 finding

LOW No provenance attestation provenance

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

v9.7.0

1 finding

LOW No provenance attestation provenance

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

v9.6.0

1 finding

LOW No provenance attestation provenance

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

v9.5.0

1 finding

LOW No provenance attestation provenance

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

v9.4.0

1 finding

LOW No provenance attestation provenance

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

v9.3.0

1 finding

LOW No provenance attestation provenance

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

v9.2.0

1 finding

LOW No provenance attestation provenance

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

v9.1.1

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@eslint/js' is 1 edit(s) away from popular package 'qs'.

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.

v9.1.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@eslint/js' is 1 edit(s) away from popular package 'qs'.

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.

v9.0.0

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

Package name '@eslint/js' is 1 edit(s) away from popular package 'qs'.

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.