@gooddata/stylelint-config
GoodData CSS Style Guide
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:rodri360.com | AI (email-domain): Long-established GoodData org package; stale maintainer email is a hygiene issue, not an active threat vector given the CI publisher track record. | ai | |
| phantom-deps | phantom-dep:stylelint | AI (phantom-deps): Stylelint config package; deps are referenced in .stylelintrc config, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:postcss-scss | AI (phantom-deps): Stylelint config package; deps are referenced in .stylelintrc config, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-scss | AI (phantom-deps): Stylelint config package; deps are referenced in .stylelintrc config, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Stylelint config package; deps are referenced in .stylelintrc config, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-config-standard | AI (phantom-deps): Stylelint config package; deps are referenced in .stylelintrc config, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-plugin-defensive-css | AI (phantom-deps): Stylelint config package; deps are referenced in .stylelintrc config, not JS imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-order | AI (phantom-deps): Stylelint config package; deps are referenced in .stylelintrc config, not JS imports. Stable FP for this package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 11.40.0 | 7 / 0 | |
| 11.39.0 | 7 / 0 | |
| 11.38.0 | 7 / 0 | |
| 11.37.0 | 7 / 0 | |
| 11.36.0 | 7 / 0 | |
| 11.35.0 | 7 / 0 | |
| 11.34.0 | 7 / 0 | |
| 11.33.0 | 7 / 0 | |
| 11.32.0 | 7 / 0 | |
| 11.31.0 | 7 / 0 | |
| 11.30.0 | 7 / 0 | |
| 11.29.0 | 7 / 0 | |
| 11.28.0 | 7 / 0 | |
| 11.27.0 | 7 / 0 | |
| 11.26.0 | 7 / 0 | |
| 11.25.0 | 7 / 0 | |
| 11.24.0 | 7 / 0 | |
| 11.23.0 | 7 / 0 | |
| 11.22.0 | 7 / 0 | |
| 11.21.0 | 7 / 0 | |
| 11.20.0 | 7 / 0 | |
| 11.19.0 | 6 / 0 |
v11.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.36.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.35.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.34.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.33.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.30.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.29.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.28.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.27.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.26.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.25.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.24.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.23.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.22.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.21.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.20.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.19.0
2 findingsMaintainer email '[email protected]' uses domain 'rodri360.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.