@csstools/postcss-text-decoration-shorthand MIT-0 25 versions

@csstools/postcss-text-decoration-shorthand

npm Repository Homepage

Use text-decoration in it's shorthand form in CSS

25

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

csspostcss-pluginshorthandtext-decorationtext-decoration-thickness

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from alaguna to romainmenke is a documented, legitimate transition within the csstools org; both are listed as contributors in package.json.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is a well-established csstools maintainer (1198 approved packages, 0 rejected); addition reflects legitimate org-level maintainer management.	ai	2026/04/24
license	uncommon-license:MIT-0	AI (license): MIT-0 is a recognized permissive license (no-attribution MIT variant); not a security concern for this package.	ai	2026/04/24

Versions (showing 25 of 25)

Version	Deps	Published
5.0.3	2 / 0	2026-02-21
5.0.2	2 / 0	2026-02-06
5.0.1	2 / 0	2026-01-25
5.0.0	2 / 0	2026-01-14
4.0.3	2 / 0	2025-08-22
4.0.2	2 / 0	2025-02-23
4.0.1	2 / 0	2024-08-14
4.0.0	2 / 0	2024-08-03
3.0.7	2 / 0	2024-06-29
3.0.6	2 / 0	2024-04-21
3.0.5	2 / 0	2024-03-31
3.0.4	2 / 0	2023-12-15
3.0.3	2 / 2	2023-09-18
3.0.2	2 / 2	2023-09-02
3.0.1	2 / 2	2023-08-28
3.0.0	2 / 2	2023-07-03
2.2.4	2 / 2	2023-05-19
2.2.3	2 / 2	2023-04-10
2.2.2	2 / 2	2023-03-25
2.2.1	2 / 1	2023-02-13
2.2.0	2 / 1	2023-02-02
2.1.0	1 / 1	2023-01-28
2.0.1	1 / 1	2023-01-28
2.0.0	1 / 1	2023-01-24
1.0.0	1 / 1	2022-08-15

v5.0.2

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

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.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

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. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.7

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.6

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2024-04-21) provenance

This version was published by a different npm account than previous versions on 2024-04-21. 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.5

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2024-03-31) provenance

This version was published by a different npm account than previous versions on 2024-03-31. 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.4

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.3

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.2

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-09-02) provenance

This version was published by a different npm account than previous versions on 2023-09-02. 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-08-28) provenance

This version was published by a different npm account than previous versions on 2023-08-28. 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.2.4

1 finding

LOW No provenance attestation provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.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. Consider requesting the maintainer enable provenance via CI/CD.

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.