@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 8 of 119)
| Version | Deps | Published |
|---|---|---|
| 4.80.4 | 10 / 5 | |
| 4.80.3 | 10 / 5 | |
| 4.80.2 | 10 / 5 | |
| 4.80.1 | 10 / 5 | |
| 4.80.0 | 10 / 5 | |
| 4.79.2 | 10 / 5 | |
| 4.79.1 | 10 / 5 | |
| 4.79.0 | 10 / 5 |
v4.80.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.80.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.80.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.
v4.80.1
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.80.0
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.79.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.
v4.79.1
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.79.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.