eslint — Greenflagged

An AST-based pattern checker for JavaScript.

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

astlintjavascriptecmascriptespree

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:lib/util/unicode/is-combining-character.js	AI (source-diff): Generated Unicode combining character data file — a dense integer array, not obfuscated malware. Explicitly labeled as auto-generated by tools/update-unicode-utils.js. Stable false positive for ESLint.	ai	2026/04/22
source-diff	net-exec-file:lib/util/ast-utils.js	AI (source-diff): lib/util/ast-utils.js is a core ESLint AST utility file with no actual network calls or malicious code execution — only standard require() and AST pattern matching. False positive for this package.	ai	2026/04/22
dependencies	unvetted-dep:handlebars	AI (dependencies): handlebars ^4.0.0 is a stable, widely-used template engine; appropriate for eslint's config generation.	ai	2026/04/22
source-diff	obfuscated-file:lib/util/patterns/letters.js	AI (source-diff): File is a machine-generated Unicode letter regex using the `regenerate` library, explicitly documented as such in the file header. Long lines are inherent to this generation approach, not obfuscation.	ai	2026/04/22
provenance	publisher-changed	AI (provenance): ivolodin (Ilya Volodin) is a long-standing ESLint core team member with 181 approved packages. Multi-maintainer releases are normal for the ESLint project.	ai	2026/04/22
provenance	missing-githead	AI (provenance): eslint 2.0.0 is a major release from the canonical publisher; missing gitHead is consistent with a changed publish workflow for a major version and is not a malware signal for this well-established package.	ai	2026/04/22
semgrep	semgrep:child-process-import	AI (semgrep): child_process is legitimately used in config-initializer for CLI tool initialization; stable pattern for eslint.	ai	2026/04/22
phantom-deps	phantom-dep:estraverse	AI (phantom-deps): estraverse is explicitly declared as a runtime dependency in package.json; the phantom-dep finding is a false positive for this package.	ai	2026/04/22
source-diff	source-size-tripled	AI (source-diff): ESLint is a large, actively developed linting tool. Early versions grew rapidly as rules and infrastructure were added. Size increases reflect legitimate feature growth, not injected payloads.	ai	2026/04/22
dependencies	unvetted-dep:cssauron-esprima	AI (dependencies): cssauron-esprima is a small, specialized esprima wrapper; pinned to 0.0.1 and appropriate for eslint's AST analysis needs.	ai	2026/04/22
source-diff	net-exec-file:lib/types/rules.d.ts	AI (source-diff): lib/types/rules.d.ts is a TypeScript declaration file with only type definitions; no actual network calls or code execution. The analyzer false-positived on type signatures in a .d.ts file.	ai	2026/04/22
source-diff	obfuscated-file:lib/rules/utils/patterns/letters.js	AI (source-diff): Generated Unicode regex pattern with documented provenance from JSCS/regenerate tooling; long lines are the pattern itself, not obfuscation.	ai	2026/04/22
phantom-deps	phantom-dep:@types/json-schema	AI (phantom-deps): TypeScript type packages are loaded by convention; acceptable for a tool providing type definitions.	ai	2026/04/22
source-diff	net-exec-file:lib/types/rules/best-practices.d.ts	AI (source-diff): File is a TypeScript definition extracted from @types/eslint; contains only type declarations and MIT license header, no executable code or network calls.	ai	2026/04/22
dependencies	unvetted-dep:@nodelib/fs.walk	AI (dependencies): Established filesystem utility; appropriate for eslint's file-walking operations.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): OpenJS Foundation addition reflects ESLint's documented governance transition; legitimate organizational change.	ai	2026/04/21
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of prior maintainers is consistent with OpenJS Foundation takeover; not a compromise signal.	ai	2026/04/21
source-diff	large-new-source-files	AI (source-diff): 75 new source files expected for a v7→v10 major version jump including new flat config system, TypeScript types, and rule refactoring.	ai	2026/04/21
publish-pattern	dormant-publish	AI (publish-pattern): Apparent dormancy is an artifact of the registry's last approved version being v7.32.0; ESLint published v8.x and v9.x continuously. Not actual inactivity.	ai	2026/04/21
publish-pattern	new-deps-added	AI (publish-pattern): @eslint/config-array is an internal eslint package; new dependency is legitimate for this major version.	ai	2026/04/21
phantom-deps	phantom-dep:import-fresh	AI (phantom-deps): Normal pattern for config loaders; referenced in config files, not directly imported.	ai	2026/04/21
phantom-deps	phantom-dep:strip-json-comments	AI (phantom-deps): Normal pattern for config loaders; referenced in config files, not directly imported.	ai	2026/04/21
dependencies	unvetted-dep:v8-compile-cache	AI (dependencies): v8-compile-cache is a well-known performance optimization package used by eslint; legitimate and stable dependency.	ai	2026/04/21
dependencies	unvetted-dep:@eslint/eslintrc	AI (dependencies): @eslint/eslintrc is an official eslint org package for config handling; legitimate and stable dependency.	ai	2026/04/21
dependencies	unvetted-dep:eslint-utils	AI (dependencies): eslint-utils is a core eslint ecosystem utility package; legitimate and stable dependency.	ai	2026/04/21
dependencies	unvetted-dep:regexpp	AI (dependencies): regexpp is a well-known regex parser used by eslint for rule analysis; legitimate and stable dependency.	ai	2026/04/21
dependencies	unvetted-dep:table	AI (dependencies): table is a well-known, legitimate runtime dependency of eslint used for formatting output; stable across eslint versions.	ai	2026/04/21
dependencies	unvetted-dep:functional-red-black-tree	AI (dependencies): functional-red-black-tree is a well-known data structure package used by eslint; legitimate and stable dependency.	ai	2026/04/21
dependencies	unvetted-dep:@humanwhocodes/config-array	AI (dependencies): @humanwhocodes/config-array is authored by eslint's creator Nicholas Zakas and is a legitimate eslint dependency; stable for this package.	ai	2026/04/21
phantom-deps	phantom-dep:@types/estree	AI (phantom-deps): TypeScript type packages are loaded by convention; acceptable for a tool providing type definitions.	ai	2026/04/21
semgrep	semgrep:dynamic-require	AI (semgrep): Loads internal message templates from fixed directory; template name from error objects, not user input.	ai	2026/04/21
provenance	no-provenance	AI (provenance): ESLint is a well-established package with a known publisher and repository. Lack of Sigstore provenance is not a meaningful risk signal here.	ai	2026/04/21

Versions (showing 100 of 356)

Hide prereleases

Version	Deps	Published
4.18.2	37 / 38	2018-03-02
4.18.1	37 / 38	2018-02-20
4.18.0	37 / 38	2018-02-16
4.17.0	37 / 38	2018-02-03
4.16.0	37 / 38	2018-01-20
4.15.0	37 / 38	2018-01-07
4.14.0	37 / 38	2017-12-23
4.13.1	37 / 38	2017-12-11
4.13.0	37 / 38	2017-12-08
4.12.1	37 / 38	2017-11-30
4.12.0	37 / 38	2017-11-26
4.11.0	37 / 38	2017-11-10
4.10.0	37 / 37	2017-10-27
4.9.0	37 / 37	2017-10-14
4.8.0	37 / 37	2017-09-29
4.7.2	37 / 37	2017-09-21
4.7.1	37 / 37	2017-09-18
4.7.0	37 / 37	2017-09-15
4.6.1	37 / 37	2017-09-03
4.6.0	37 / 37	2017-09-01
4.5.0	37 / 37	2017-08-19
4.4.1	36 / 37	2017-08-07
4.4.0	36 / 37	2017-08-05
4.3.0	36 / 37	2017-07-21
4.2.0	33 / 37	2017-07-09
4.1.1	33 / 37	2017-06-26
4.1.0	33 / 37	2017-06-24
4.0.0	32 / 37	2017-06-12
3.19.0	35 / 36	2017-03-31
3.18.0	35 / 36	2017-03-17
3.17.1	34 / 36	2017-03-06
3.17.0	34 / 35	2017-03-03
3.16.1	34 / 37	2017-02-22
3.16.0	34 / 37	2017-02-20
3.15.0	34 / 37	2017-02-03
3.14.1	34 / 37	2017-01-25
3.14.0	34 / 37	2017-01-20
3.13.1	34 / 37	2017-01-09
3.13.0	34 / 37	2017-01-06
3.12.2	34 / 37	2016-12-14
3.12.1	34 / 37	2016-12-12
3.12.0	34 / 37	2016-12-09
3.11.1	34 / 37	2016-11-28
3.11.0	34 / 37	2016-11-25
3.10.2	34 / 37	2016-11-15
3.10.1	34 / 37	2016-11-14
3.10.0	34 / 37	2016-11-11
3.9.1	34 / 37	2016-10-31
3.9.0	34 / 37	2016-10-28
3.8.1	33 / 37	2016-10-17
3.8.0	33 / 37	2016-10-14
3.7.1	33 / 37	2016-10-03
3.7.0	33 / 37	2016-09-30
3.6.1	33 / 37	2016-09-26
3.6.0	33 / 37	2016-09-23
3.5.0	33 / 37	2016-09-09
3.4.0	33 / 37	2016-08-26
3.3.1	33 / 37	2016-08-15
3.3.0	33 / 37	2016-08-12
3.2.2	32 / 36	2016-08-01
3.2.1	33 / 36	2016-08-01
3.2.0	32 / 36	2016-07-29
3.1.1	33 / 32	2016-07-18
3.1.0	33 / 32	2016-07-15
3.0.1	33 / 32	2016-07-05
3.0.0	33 / 32	2016-07-01
2.13.1	33 / 32	2016-06-20
2.13.0	33 / 32	2016-06-17
2.12.0	33 / 31	2016-06-10
2.11.1	33 / 31	2016-05-30
2.11.0	32 / 31	2016-05-27
2.10.2	32 / 31	2016-05-16
2.10.1	32 / 28	2016-05-14
2.10.0	32 / 28	2016-05-13
2.9.0	32 / 28	2016-04-29
2.8.0	32 / 28	2016-04-15
2.7.0	32 / 28	2016-04-04
2.6.0	32 / 28	2016-04-01
2.5.3	33 / 28	2016-03-28
2.5.2	33 / 28	2016-03-28
2.5.1	33 / 28	2016-03-25
2.5.0	33 / 28	2016-03-25
2.4.0	32 / 29	2016-03-11
2.3.0	32 / 29	2016-03-05
2.2.0	33 / 30	2016-02-19
2.1.0	32 / 29	2016-02-15
2.0.0	32 / 28	2016-02-12
1.10.0	33 / 28	2015-11-20
1.2.1	27 / 25	2015-08-20
1.2.0	27 / 25	2015-08-18
1.1.0	26 / 24	2015-08-07
1.0.0	26 / 24	2015-07-31
0.24.1	22 / 23	2015-07-10
0.24.0	22 / 23	2015-06-26
0.23.0	22 / 23	2015-06-15
0.22.1	22 / 23	2015-05-31
0.22.0	22 / 23	2015-05-30
0.21.2	21 / 22	2015-05-18
0.21.1	21 / 22	2015-05-15
0.21.0	21 / 22	2015-05-09

Showing 100 of 356 Next page →

v4.18.2

1 finding

INFO No provenance attestation provenance

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

v4.18.1

1 finding

INFO No provenance attestation provenance

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

v4.18.0

1 finding

INFO No provenance attestation provenance

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

v4.17.0

1 finding

INFO No provenance attestation provenance

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

v4.16.0

1 finding

INFO No provenance attestation provenance

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

v4.15.0

1 finding

INFO No provenance attestation provenance

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

v4.14.0

1 finding

INFO No provenance attestation provenance

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

v4.13.1

1 finding

INFO No provenance attestation provenance

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

v4.13.0

1 finding

INFO No provenance attestation provenance

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

v4.12.1

1 finding

INFO No provenance attestation provenance

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

v4.12.0

1 finding

INFO No provenance attestation provenance

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

v4.11.0

1 finding

INFO No provenance attestation provenance

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

v4.10.0

1 finding

INFO No provenance attestation provenance

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

v4.9.0

1 finding

INFO No provenance attestation provenance

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

v4.8.0

1 finding

INFO No provenance attestation provenance

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

v4.7.2

1 finding

INFO No provenance attestation provenance

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

v4.7.1

1 finding

INFO No provenance attestation provenance

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

v4.7.0

1 finding

INFO No provenance attestation provenance

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

v4.6.1

1 finding

INFO No provenance attestation provenance

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

v4.6.0

1 finding

INFO No provenance attestation provenance

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

v4.5.0

1 finding

INFO No provenance attestation provenance

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

v4.4.1

1 finding

INFO No provenance attestation provenance

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

v4.4.0

1 finding

INFO No provenance attestation provenance

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

v4.3.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v4.2.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v4.1.1

1 finding

INFO No provenance attestation provenance

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

v4.1.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v4.0.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.19.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.18.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.17.1

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.17.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.16.1

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.16.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.15.0

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.14.1

2 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.14.0

3 findings

HIGH Publisher changed: nzakas → eslint (on 2017-01-20) provenance

This version was published by a different npm account than previous versions on 2017-01-20. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.13.1

3 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2017-01-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-01-09. This could indicate a legitimate maintainer transition or an account compromise.

v3.13.0

3 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2017-01-06) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-01-06. This could indicate a legitimate maintainer transition or an account compromise.

v3.12.2

3 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-12-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-12-14. This could indicate a legitimate maintainer transition or an account compromise.

v3.12.1

3 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-12-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-12-12. This could indicate a legitimate maintainer transition or an account compromise.

v3.12.0

3 findings

HIGH Publisher changed: nzakas → eslint (on 2016-12-09) provenance

This version was published by a different npm account than previous versions on 2016-12-09. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

v3.11.1

3 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-11-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-28. This could indicate a legitimate maintainer transition or an account compromise.

v3.11.0

3 findings

HIGH New obfuscated file: lib/util/patterns/letters.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-11-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-25. This could indicate a legitimate maintainer transition or an account compromise.

v3.10.2

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-11-15) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-15. This could indicate a legitimate maintainer transition or an account compromise.

v3.10.1

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-11-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-14. This could indicate a legitimate maintainer transition or an account compromise.

v3.10.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-11-11) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-11-11. This could indicate a legitimate maintainer transition or an account compromise.

v3.9.1

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-10-31) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-31. This could indicate a legitimate maintainer transition or an account compromise.

v3.9.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-10-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-28. This could indicate a legitimate maintainer transition or an account compromise.

v3.8.1

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: nzakas → eslint (on 2016-10-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-17. This could indicate a legitimate maintainer transition or an account compromise.

v3.8.0

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-10-14) provenance

This version was published by a different npm account than previous versions on 2016-10-14. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.7.1

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-10-03) provenance

This version was published by a different npm account than previous versions on 2016-10-03. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.7.0

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-09-30) provenance

This version was published by a different npm account than previous versions on 2016-09-30. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.6.1

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-09-26) provenance

This version was published by a different npm account than previous versions on 2016-09-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.6.0

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-09-23) provenance

This version was published by a different npm account than previous versions on 2016-09-23. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.5.0

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-09-09) provenance

This version was published by a different npm account than previous versions on 2016-09-09. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.4.0

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-08-26) provenance

This version was published by a different npm account than previous versions on 2016-08-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.3.1

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-08-15) provenance

This version was published by a different npm account than previous versions on 2016-08-15. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.3.0

2 findings

HIGH Publisher changed: nzakas → eslint (on 2016-08-12) provenance

This version was published by a different npm account than previous versions on 2016-08-12. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.2.2

1 finding

INFO No provenance attestation provenance

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

v3.2.1

1 finding

INFO No provenance attestation provenance

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

v3.2.0

1 finding

INFO No provenance attestation provenance

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

v3.1.1

1 finding

INFO No provenance attestation provenance

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

v3.1.0

2 findings

HIGH Publisher changed: nzakas → ivolodin (on 2016-07-15) provenance

This version was published by a different npm account than previous versions on 2016-07-15. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.0.1

1 finding

INFO No provenance attestation provenance

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

v3.0.0

1 finding

INFO No provenance attestation provenance

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

v2.13.1

1 finding

INFO No provenance attestation provenance

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

v2.13.0

1 finding

INFO No provenance attestation provenance

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

v2.12.0

1 finding

INFO No provenance attestation provenance

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

v2.11.1

1 finding

INFO No provenance attestation provenance

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

v2.11.0

1 finding

INFO No provenance attestation provenance

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

v2.10.2

1 finding

INFO No provenance attestation provenance

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

v2.10.1

2 findings

HIGH Publisher changed: nzakas → ivolodin (on 2016-05-14) provenance

This version was published by a different npm account than previous versions on 2016-05-14. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v2.10.0

2 findings

HIGH Publisher changed: nzakas → ivolodin (on 2016-05-13) provenance

This version was published by a different npm account than previous versions on 2016-05-13. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v2.9.0

1 finding

INFO No provenance attestation provenance

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

v2.8.0

1 finding

INFO No provenance attestation provenance

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

v2.7.0

2 findings

HIGH Publisher changed: nzakas → ivolodin (on 2016-04-04) provenance

This version was published by a different npm account than previous versions on 2016-04-04. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v2.6.0

1 finding

INFO No provenance attestation provenance

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

v2.5.3

1 finding

INFO No provenance attestation provenance

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

v2.5.2

1 finding

INFO No provenance attestation provenance

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

v2.5.1

1 finding

INFO No provenance attestation provenance

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

v2.5.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nzakas.

INFO No provenance attestation provenance

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

v2.4.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nzakas.

INFO No provenance attestation provenance

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

v2.3.0

2 findings

HIGH Publisher changed: nzakas → ivolodin (on 2016-03-05) provenance

This version was published by a different npm account than previous versions on 2016-03-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v2.2.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nzakas.

INFO No provenance attestation provenance

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

v2.1.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nzakas.

INFO No provenance attestation provenance

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

v2.0.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: nzakas.

INFO No provenance attestation provenance

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

v1.10.0

1 finding

INFO No provenance attestation provenance

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

v1.2.1

1 finding

INFO No provenance attestation provenance

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

v1.2.0

1 finding

INFO No provenance attestation provenance

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

v1.1.0

1 finding

INFO No provenance attestation provenance

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

v1.0.0

1 finding

INFO No provenance attestation provenance

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

v0.24.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.24.0

1 finding

INFO No provenance attestation provenance

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

v0.23.0

2 findings

HIGH Publisher changed: nzakas → ivolodin (on 2015-06-15) provenance

This version was published by a different npm account than previous versions on 2015-06-15. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.22.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ivolodin.

HIGH Publisher changed: nzakas → ivolodin (on 2015-05-31) provenance

This version was published by a different npm account than previous versions on 2015-05-31. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.22.0

2 findings

HIGH Publisher changed: nzakas → ivolodin (on 2015-05-30) provenance

This version was published by a different npm account than previous versions on 2015-05-30. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.21.2

1 finding

INFO No provenance attestation provenance

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

v0.21.1

1 finding

INFO No provenance attestation provenance

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

v0.21.0

1 finding

INFO No provenance attestation provenance

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