@newhighsco/postcss-config
New High Score shareable config for PostCSS
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:autoprefixer | AI (phantom-deps): PostCSS config package; plugins are loaded by PostCSS at runtime, not directly imported. | ai | |
| phantom-deps | phantom-dep:caniuse-lite | AI (phantom-deps): Used transitively by postcss-preset-env; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:postcss-preset-env | AI (phantom-deps): PostCSS config package; plugins referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:postcss-flexbugs-fixes | AI (phantom-deps): PostCSS config package; plugins referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@fullhuman/postcss-purgecss | AI (phantom-deps): PostCSS config package; plugins referenced in config files, not direct imports. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 4.0.53 | 5 / 1 | |
| 4.0.52 | 5 / 1 | |
| 4.0.51 | 5 / 1 | |
| 4.0.50 | 5 / 1 | |
| 4.0.49 | 5 / 1 | |
| 4.0.48 | 5 / 1 | |
| 4.0.47 | 5 / 1 | |
| 4.0.46 | 5 / 1 | |
| 4.0.45 | 5 / 1 | |
| 4.0.44 | 5 / 1 | |
| 4.0.43 | 5 / 1 | |
| 4.0.42 | 5 / 1 | |
| 4.0.41 | 5 / 1 | |
| 4.0.40 | 5 / 1 | |
| 4.0.39 | 5 / 1 | |
| 4.0.38 | 5 / 1 | |
| 4.0.37 | 5 / 1 | |
| 4.0.36 | 5 / 1 | |
| 4.0.35 | 5 / 1 | |
| 4.0.34 | 5 / 1 | |
| 4.0.33 | 5 / 1 | |
| 4.0.32 | 5 / 1 | |
| 4.0.31 | 5 / 1 | |
| 4.0.30 | 5 / 1 | |
| 4.0.29 | 5 / 1 | |
| 4.0.28 | 5 / 1 | |
| 4.0.27 | 5 / 1 | |
| 4.0.26 | 5 / 1 | |
| 4.0.25 | 5 / 1 | |
| 4.0.24 | 5 / 1 | |
| 4.0.23 | 5 / 1 | |
| 4.0.22 | 5 / 1 | |
| 4.0.21 | 5 / 1 | |
| 4.0.20 | 5 / 1 | |
| 4.0.19 | 5 / 1 | |
| 4.0.18 | 5 / 1 | |
| 4.0.17 | 5 / 1 | |
| 4.0.16 | 5 / 1 | |
| 4.0.15 | 5 / 1 | |
| 4.0.14 | 5 / 1 | |
| 4.0.13 | 5 / 1 | |
| 4.0.12 | 5 / 1 | |
| 4.0.11 | 5 / 1 | |
| 4.0.10 | 5 / 1 | |
| 4.0.9 | 5 / 1 | |
| 4.0.8 | 5 / 1 | |
| 4.0.7 | 5 / 1 | |
| 4.0.6 | 5 / 1 | |
| 4.0.5 | 5 / 1 | |
| 4.0.4 | 5 / 1 | |
| 4.0.3 | 5 / 1 | |
| 4.0.2 | 5 / 1 | |
| 4.0.1 | 5 / 1 | |
| 4.0.0 | 5 / 1 |
v4.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.