@knapsack/postcss-config-starter
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:postcss-assets | AI (dependencies): Legitimate PostCSS plugin; stable dependency across many versions of this package. | ai | |
| dependencies | unvetted-dep:postcss-utilities | AI (dependencies): Legitimate PostCSS plugin; stable dependency across many versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; consistent with this package's publish history. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description across all versions of this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of large established @knapsack monorepo; sparse metadata is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:postcss-assets | AI (phantom-deps): Config-file-referenced PostCSS plugin; not directly imported by design in a config starter package. | ai | |
| phantom-deps | phantom-dep:postcss-utilities | AI (phantom-deps): Config-file-referenced PostCSS plugin; not directly imported by design in a config starter package. | ai |
Versions (showing 51 of 108)
| Version | Deps | Published |
|---|---|---|
| 4.93.0 | 10 / 5 | |
| 4.92.24 | 10 / 5 | |
| 4.92.23 | 10 / 5 | |
| 4.92.22 | 10 / 5 | |
| 4.92.21 | 10 / 5 | |
| 4.92.20 | 10 / 5 | |
| 4.92.19 | 10 / 5 | |
| 4.92.18 | 10 / 5 | |
| 4.92.17 | 10 / 5 | |
| 4.92.16 | 10 / 5 | |
| 4.92.15 | 10 / 5 | |
| 4.92.14 | 10 / 5 | |
| 4.92.13 | 10 / 5 | |
| 4.92.12 | 10 / 5 | |
| 4.92.11 | 10 / 5 | |
| 4.92.10 | 10 / 5 | |
| 4.92.9 | 10 / 5 | |
| 4.92.8 | 10 / 5 | |
| 4.92.7 | 10 / 5 | |
| 4.92.6 | 10 / 5 | |
| 4.92.5 | 10 / 5 | |
| 4.92.4 | 10 / 5 | |
| 4.92.3 | 10 / 5 | |
| 4.92.2 | 10 / 5 | |
| 4.92.1 | 10 / 5 | |
| 4.92.0 | 10 / 5 | |
| 4.91.0 | 10 / 5 | |
| 4.90.0 | 10 / 5 | |
| 4.89.13 | 10 / 5 | |
| 4.89.12 | 10 / 5 | |
| 4.89.11 | 10 / 5 | |
| 4.89.10 | 10 / 5 | |
| 4.89.9 | 10 / 5 | |
| 4.89.8 | 10 / 5 | |
| 4.89.7 | 10 / 5 | |
| 4.89.6 | 10 / 5 | |
| 4.89.5 | 10 / 5 | |
| 4.89.4 | 10 / 5 | |
| 4.89.3 | 10 / 5 | |
| 4.89.2 | 10 / 5 | |
| 4.89.1 | 10 / 5 | |
| 4.89.0 | 10 / 5 | |
| 4.88.0 | 10 / 5 | |
| 4.87.9 | 10 / 5 | |
| 4.87.8 | 10 / 5 | |
| 4.87.7 | 10 / 5 | |
| 4.87.6 | 10 / 5 | |
| 4.87.5 | 10 / 5 | |
| 4.87.4 | 10 / 5 | |
| 4.87.3 | 10 / 5 | |
| 4.87.2 | 10 / 5 |
v4.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.89.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.87.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.