← Home

stylelint-config-recommended

npm Repository Homepage

Recommended shareable config for Stylelint

24
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jeddy3ybiquitousromainmenkentwb

Keywords

stylelintstylelint-configrecommended

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Stylelint org moved to GitHub Actions for automated releases; publisher-changed to GitHub Actions with SLSA provenance is the expected pattern for this package going forward. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer list consolidation is consistent with the Stylelint org's move to CI/CD-based releases; SLSA provenance confirms legitimate org-controlled publishing. ai

Versions (showing 24 of 24)

Version Deps Published
18.0.0 0 / 10
17.0.0 0 / 11
16.0.0 0 / 11
15.0.0 0 / 11
14.0.1 0 / 11
14.0.0 0 / 11
13.0.0 0 / 13
12.0.0 0 / 13
11.0.0 0 / 13
10.0.1 0 / 12
10.0.0 0 / 12
9.0.0 0 / 12
8.0.0 0 / 12
7.0.0 0 / 12
6.0.0 0 / 12
5.0.0 0 / 14
4.0.0 0 / 14
3.0.0 0 / 10
2.2.0 0 / 10
2.1.0 0 / 9
2.0.1 0 / 9
2.0.0 0 / 9
1.0.0 0 / 9
0.1.0 0 / 9

v18.0.0

2 findings
HIGH Publisher changed: jeddy3 → GitHub Actions (on 2026-01-15) provenance

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

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v17.0.0

1 finding
LOW No provenance attestation provenance

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

v16.0.0

1 finding
LOW No provenance attestation provenance

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

v15.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: ybiquitous → jeddy3 (on 2025-01-12) provenance

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

v14.0.1

1 finding
LOW No provenance attestation provenance

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