@stylistic/eslint-plugin-js
JavaScript stylistic rules for ESLint, migrated from [eslint core](https://github.com/eslint/eslint).
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Transition from eslint-community-bot/antfu/michaeldeboey to eslint-stylistic-bot is a documented migration to a dedicated CI bot for the eslint-stylistic project. SLSA provenance confirms CI-published releases. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to eslint-stylistic-bot is a legitimate project-level transition; bot account has 339 approved packages and SLSA attestation confirms integrity. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): eslint-stylistic-bot is the project's dedicated publishing bot; addition is part of the same legitimate transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of prior maintainers is consistent with consolidating publishing under the eslint-stylistic-bot CI account. | ai | |
| phantom-deps | phantom-dep:acorn | AI (phantom-deps): acorn is a transitive dependency used by espree/ESLint internals; declaring it as a direct dep for version pinning is a common and legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@types/eslint | AI (phantom-deps): @types/eslint is a type-only dependency loaded by convention in TypeScript ESLint plugins; not directly imported at runtime. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 2 / 0 | |
| 4.4.0 | 2 / 0 | |
| 4.3.0 | 2 / 0 | |
| 4.2.0 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.1 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.13.0 | 2 / 0 | |
| 2.12.1 | 2 / 0 | |
| 2.12.0 | 2 / 0 | |
| 2.11.0 | 2 / 0 | |
| 2.10.1 | 2 / 0 | |
| 2.10.0 | 2 / 0 | |
| 2.9.0 | 2 / 0 | |
| 2.8.0 | 2 / 0 | |
| 2.7.2 | 3 / 0 | |
| 2.7.1 | 3 / 0 | |
| 2.6.5 | 4 / 0 | |
| 2.6.4 | 4 / 0 | |
| 2.6.3 | 4 / 0 | |
| 2.6.2 | 4 / 3 | |
| 2.6.1 | 4 / 3 | |
| 2.6.0 | 4 / 3 | |
| 2.4.0 | 4 / 3 | |
| 2.3.0 | 4 / 3 | |
| 2.2.2 | 4 / 3 | |
| 2.2.1 | 4 / 3 | |
| 2.2.0 | 4 / 3 | |
| 2.1.0 | 4 / 3 | |
| 2.0.0 | 4 / 3 | |
| 1.8.1 | 5 / 2 | |
| 1.8.0 | 5 / 2 | |
| 1.7.2 | 5 / 2 | |
| 1.7.0 | 5 / 2 | |
| 1.6.3 | 5 / 2 | |
| 1.6.2 | 5 / 2 | |
| 1.6.1 | 4 / 2 | |
| 1.6.0 | 4 / 2 | |
| 1.5.4 | 4 / 2 | |
| 1.5.3 | 4 / 2 | |
| 1.5.1 | 4 / 2 | |
| 1.5.0 | 5 / 1 | |
| 1.4.1 | 5 / 1 | |
| 1.4.0 | 5 / 1 | |
| 1.3.3 | 5 / 1 | |
| 1.3.2 | 5 / 1 | |
| 1.3.1 | 5 / 1 | |
| 1.3.0 | 5 / 1 |
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
3 findingsAll previous maintainers (eslint-community-bot, antfu, michaeldeboey) were replaced by new maintainers (eslint-stylistic-bot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2024-05-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
3 findingsAll previous maintainers (eslint-community-bot, antfu, michaeldeboey) were replaced by new maintainers (eslint-stylistic-bot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2024-05-08. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.1
3 findingsAll previous maintainers (eslint-community-bot, antfu, michaeldeboey) were replaced by new maintainers (eslint-stylistic-bot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2024-05-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
3 findingsAll previous maintainers (eslint-community-bot, antfu, michaeldeboey) were replaced by new maintainers (eslint-stylistic-bot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2024-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.