@donmahallem/eslint-config Apache-2.0 55 versions

@donmahallem/eslint-config

npm Repository Homepage

My personal eslint. You better not use it!

55

Versions

Apache-2.0

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

donmahallem

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Package uses GitHub Actions CI/CD with SLSA attestation; publisher change from human to GHA is the documented release flow.	ai	2026/05/05
phantom-deps	phantom-dep:eslint-plugin-jsdoc	AI (phantom-deps): ESLint config packages reference plugins by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-plugin-import	AI (phantom-deps): ESLint config packages reference plugins by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-plugin-no-null	AI (phantom-deps): ESLint config packages reference plugins by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:prettier	AI (phantom-deps): ESLint config packages reference plugins/configs by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): ESLint config packages reference plugins by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-plugin-prefer-arrow	AI (phantom-deps): ESLint config packages reference plugins by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:@typescript-eslint/eslint-plugin	AI (phantom-deps): ESLint config packages reference plugins by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29
phantom-deps	phantom-dep:eslint-config-prettier	AI (phantom-deps): ESLint config packages reference plugins by name in config objects, not via direct imports — stable false positive.	ai	2026/04/29

Versions (showing 55 of 261)

Version	Deps	Published
2.3.105	12 / 17	2025-07-14
2.3.104	12 / 17	2025-07-08
2.3.103	12 / 17	2025-07-08
2.3.102	12 / 17	2025-07-07
2.3.101	12 / 17	2025-07-07
2.3.100	12 / 17	2025-07-02
2.3.99	12 / 17	2025-07-02
2.3.98	12 / 17	2025-07-01
2.3.97	12 / 17	2025-07-01
2.3.96	12 / 17	2025-06-30
2.3.95	12 / 17	2025-06-30
2.3.94	12 / 17	2025-06-27
2.3.93	12 / 17	2025-06-25
2.3.92	12 / 17	2025-06-24
2.3.91	12 / 17	2025-06-24
2.3.90	12 / 17	2025-06-24
2.3.89	12 / 17	2025-06-24
2.3.88	12 / 17	2025-06-23
2.3.87	12 / 17	2025-06-23
2.3.86	12 / 17	2025-06-23
2.3.85	12 / 17	2025-06-22
2.3.84	12 / 17	2025-06-21
2.3.83	12 / 17	2025-06-21
2.3.82	12 / 17	2025-06-18
2.3.81	12 / 17	2025-06-17
2.3.80	12 / 17	2025-06-16
2.3.79	12 / 17	2025-06-16
2.3.78	12 / 17	2025-06-13
2.3.77	12 / 17	2025-06-11
2.3.76	12 / 17	2025-06-11
2.3.75	12 / 17	2025-06-10
2.3.74	12 / 17	2025-06-09
2.3.73	12 / 17	2025-06-09
2.3.72	12 / 17	2025-06-07
2.3.71	12 / 17	2025-06-07
2.3.70	12 / 17	2025-06-07
2.3.69	12 / 17	2025-06-07
2.3.68	12 / 17	2025-06-01
2.3.67	12 / 17	2025-05-28
2.3.66	12 / 17	2025-05-27
2.3.65	12 / 17	2025-05-22
2.3.64	12 / 17	2025-05-21
2.3.63	12 / 17	2025-05-19
2.3.62	12 / 17	2025-05-15
2.3.61	12 / 17	2025-05-13
2.3.60	12 / 17	2025-05-13
2.3.59	12 / 17	2025-05-12
2.3.58	12 / 17	2025-05-10
2.3.57	12 / 17	2025-05-09
2.3.56	12 / 17	2025-05-07
2.3.55	12 / 17	2025-05-06
2.3.54	12 / 17	2025-05-05
2.3.53	12 / 17	2025-05-05
2.3.52	12 / 17	2025-04-29
2.3.51	12 / 17	2025-04-29

v2.3.105

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.

v2.3.104

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.

v2.3.103

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.

v2.3.102

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.

v2.3.101

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.

v2.3.100

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.

v2.3.99

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.

v2.3.98

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.

v2.3.97

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.

v2.3.96

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.

v2.3.95

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.

v2.3.94

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.

v2.3.93

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.

v2.3.92

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.

v2.3.91

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.

v2.3.90

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.

v2.3.89

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.

v2.3.88

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.

v2.3.87

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.

v2.3.86

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.

v2.3.85

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.

v2.3.84

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.

v2.3.83

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.

v2.3.82

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.

v2.3.81

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.

v2.3.80

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.

v2.3.79

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.

v2.3.78

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.

v2.3.77

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.

v2.3.76

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.

v2.3.75

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.

v2.3.74

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.

v2.3.73

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.

v2.3.72

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.

v2.3.71

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.

v2.3.70

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.

v2.3.69

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.

v2.3.68

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.

v2.3.67

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.

v2.3.66

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.

v2.3.65

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.

v2.3.64

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.

v2.3.63

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.

v2.3.62

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.

v2.3.61

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.

v2.3.60

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.

v2.3.59

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.

v2.3.58

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.

v2.3.57

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.

v2.3.56

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.

v2.3.55

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.

v2.3.54

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.

v2.3.53

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.

v2.3.52

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.

v2.3.51

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.