← Home

@csstools/postcss-normalize-display-values

npm Repository Homepage

Use two values display syntax for inner and outer display types.

11
Versions
MIT-0
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

jonathantnealalagunaromainmenke

Keywords

blockcssdisplayflexflowflow-rootgridinlineinline-blockinline-flexinline-gridinline-tablelist-itempostcss-pluginrubyruby-baseruby-textrun-intabletable-captiontable-cell

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): romainmenke is a well-established csstools contributor (1123 approved packages, 0 rejected) who took over publishing for the csstools org. Transition is consistent with the monorepo's known maintainer structure. ai
maintainer-change maintainer-added AI (maintainer-change): romainmenke is a trusted publisher within the csstools ecosystem; addition reflects a legitimate organizational maintainer transition. ai
license uncommon-license:MIT-0 AI (license): MIT-0 is a valid permissive license used consistently across the csstools plugin suite; not a risk indicator. ai

Versions (showing 11 of 11)

Version Deps Published
5.0.1 1 / 0
5.0.0 1 / 0
4.0.1 1 / 0
4.0.0 1 / 0
3.0.2 1 / 0
3.0.1 1 / 1
3.0.0 1 / 1
2.0.1 1 / 0
2.0.0 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.2

2 findings
HIGH Publisher changed: alaguna → romainmenke (on 2023-12-15) provenance

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

LOW No provenance attestation provenance

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

v3.0.1

2 findings
HIGH Publisher changed: alaguna → romainmenke (on 2023-09-18) provenance

This version was published by a different npm account than previous versions on 2023-09-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.