postcss-initial
PostCSS plugin to fallback initial keyword.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established package with clean history; missing gitHead is a minor publish-environment change, not a malware indicator. No other risk signals present. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): postcss is the core framework this plugin extends; adding it as a runtime dep is expected and benign for a PostCSS plugin package. | ai | |
| provenance | no-provenance | AI (provenance): Package is nearly 11 years old; lack of Sigstore provenance is expected for packages predating the feature. No other risk signals present. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 0 / 6 | |
| 4.0.0 | 1 / 6 | |
| 3.0.4 | 1 / 5 | |
| 3.0.3 | 1 / 5 | |
| 3.0.2 | 2 / 5 | |
| 3.0.1 | 2 / 3 | |
| 3.0.0 | 2 / 3 | |
| 2.0.0 | 2 / 3 | |
| 1.5.3 | 2 / 3 | |
| 1.5.2 | 2 / 3 | |
| 1.5.1 | 2 / 3 | |
| 1.5.0 | 2 / 3 | |
| 1.4.1 | 2 / 3 | |
| 1.4.0 | 2 / 5 | |
| 1.3.1 | 2 / 5 | |
| 1.3.0 | 2 / 5 |
v3.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: maximkoretskiy.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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.
v1.5.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.
v1.5.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.
v1.5.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.
v1.5.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.
v1.4.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.
v1.4.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.
v1.3.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.
v1.3.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.