← Home

postcss-reporter

npm Repository Homepage

Log PostCSS messages in the console

28
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

davidtheclarkai

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed from davidtheclark to ai (Andrey Sitnik, PostCSS creator). Legitimate transfer within the postcss GitHub org. ai
maintainer-change maintainer-added AI (maintainer-change): ai (Andrey Sitnik) is the PostCSS creator/maintainer; adding them to postcss-reporter is expected org maintenance. ai
provenance missing-githead AI (provenance): Publisher 'ai' (Andrey Sitnik) routinely publishes from local env; missing gitHead is consistent with his workflow across PostCSS packages. ai
provenance no-provenance AI (provenance): Established package predates provenance tooling; informational only. ai
publish-pattern new-deps-added AI (publish-pattern): Major version bump replacing monolithic lodash with individual method packages and chalk with colorette — all well-established deps. Normal refactor pattern. ai

Versions (showing 28 of 28)

Version Deps Published
7.1.0 2 / 0
7.0.5 2 / 0
7.0.4 6 / 0
7.0.3 6 / 0
7.0.2 6 / 0
7.0.1 7 / 0
7.0.0 7 / 0
6.0.1 4 / 0
6.0.0 4 / 6
5.0.0 4 / 6
4.0.0 3 / 6
3.0.0 4 / 5
2.0.0 4 / 5
1.4.1 4 / 5
1.4.0 4 / 5
1.3.3 4 / 5
1.3.2 4 / 5
1.3.1 4 / 3
1.3.0 4 / 3
1.2.1 6 / 4
1.2.0 6 / 4
1.1.0 6 / 4
1.0.0 6 / 4
0.4.0 6 / 4
0.3.1 6 / 4
0.3.0 6 / 4
0.2.0 4 / 4
0.1.0 3 / 4

v7.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ai.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ai.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ai.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ai.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.1

3 findings
HIGH Publisher changed: davidtheclark → ai (on 2018-12-30) provenance

This version was published by a different npm account than previous versions on 2018-12-30. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ai.

v6.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.