@smg-automotive/eslint-config MIT 36 versions

@smg-automotive/eslint-config

npm Repository Homepage

A boilerplate package setup

36

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

smg-automotive-engineering

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:eslint	AI (phantom-deps): Config package; eslint is referenced in configs, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:prettier	AI (phantom-deps): Config package; prettier referenced in configs, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:@eslint/eslintrc	AI (phantom-deps): Config package; framework-scoped package loaded by convention.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-config-next	AI (phantom-deps): Config package; referenced in configs, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-config-prettier	AI (phantom-deps): Config package; referenced in configs, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:@typescript-eslint/parser	AI (phantom-deps): Config package; referenced in configs, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:@typescript-eslint/eslint-plugin	AI (phantom-deps): Config package; referenced in configs, not direct imports.	ai	2026/04/30
phantom-deps	phantom-dep:eslint-import-resolver-typescript	AI (phantom-deps): Config package; referenced in configs, not direct imports.	ai	2026/04/30

Versions (showing 36 of 36)

Version	Deps	Published
6.0.10	22 / 5	2026-06-09
6.0.9	22 / 5	2026-05-21
6.0.8	22 / 5	2026-05-19
6.0.7	22 / 5	2026-05-15
6.0.6	22 / 5	2026-05-15
6.0.5	22 / 5	2026-05-15
6.0.4	22 / 5	2026-05-15
6.0.3	22 / 5	2026-05-05
6.0.2	22 / 5	2026-04-28
6.0.1	22 / 5	2026-04-20
6.0.0	22 / 5	2026-04-17
5.3.12	21 / 5	2026-04-17
5.3.11	21 / 5	2026-04-17
5.3.10	21 / 5	2026-04-15
5.3.9	21 / 5	2026-04-14
5.3.8	21 / 5	2026-04-07
5.3.7	21 / 5	2026-04-07
5.3.6	21 / 5	2026-03-31
5.3.5	21 / 5	2026-03-24
5.3.4	21 / 5	2026-03-24
5.3.3	21 / 5	2026-03-17
5.3.2	21 / 5	2026-03-16
5.3.1	21 / 5	2026-03-16
5.3.0	21 / 5	2026-03-16
5.2.15	21 / 5	2026-03-10
5.2.14	21 / 5	2026-03-04
5.2.13	21 / 5	2026-03-03
5.2.12	21 / 5	2026-03-03
5.2.11	21 / 5	2026-02-04
5.2.10	21 / 5	2026-02-03
5.2.9	21 / 5	2026-01-28
5.2.8	21 / 5	2026-01-28
5.2.7	21 / 5	2026-01-13
5.2.5	21 / 5	2025-11-25
5.2.4	21 / 5	2025-11-05
5.2.3	21 / 5	2025-11-04

v6.0.10

1 finding

LOW No provenance attestation provenance

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

v6.0.9

1 finding

LOW No provenance attestation provenance

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

v6.0.8

1 finding

LOW No provenance attestation provenance

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

v6.0.7

1 finding

LOW No provenance attestation provenance

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

v6.0.6

1 finding

LOW No provenance attestation provenance

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

v6.0.5

1 finding

LOW No provenance attestation provenance

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

v6.0.4

1 finding

LOW No provenance attestation provenance

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

v6.0.3

1 finding

LOW No provenance attestation provenance

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

v6.0.1

1 finding

LOW No provenance attestation provenance

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

v6.0.0

1 finding

LOW No provenance attestation provenance

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

v5.3.12

1 finding

LOW No provenance attestation provenance

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

v5.3.11

1 finding

LOW No provenance attestation provenance

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

v5.3.10

1 finding

LOW No provenance attestation provenance

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

v5.3.9

1 finding

LOW No provenance attestation provenance

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

v5.3.8

1 finding

LOW No provenance attestation provenance

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

v5.3.7

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.

v5.3.6

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.

v5.3.5

1 finding

LOW No provenance attestation provenance

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

v5.3.4

1 finding

LOW No provenance attestation provenance

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

v5.3.3

1 finding

LOW No provenance attestation provenance

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

v5.3.2

1 finding

LOW No provenance attestation provenance

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

v5.3.1

1 finding

LOW No provenance attestation provenance

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

v5.3.0

1 finding

LOW No provenance attestation provenance

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

v5.2.15

1 finding

LOW No provenance attestation provenance

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

v5.2.14

1 finding

LOW No provenance attestation provenance

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

v5.2.13

1 finding

LOW No provenance attestation provenance

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

v5.2.12

1 finding

LOW No provenance attestation provenance

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

v5.2.11

1 finding

LOW No provenance attestation provenance

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

v5.2.10

1 finding

LOW No provenance attestation provenance

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

v5.2.9

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.

v5.2.8

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.

v5.2.7

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.

v5.2.5

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.

v5.2.4

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.

v5.2.3

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.