@csstools/postcss-oklab-function MIT-0 50 versions

@csstools/postcss-oklab-function

npm Repository Homepage

Use oklab() and oklch() color functions in CSS

50

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

colorcssdesigndisplay-p3oklaboklchpostcsspostcss-pluginsyntax

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 csstools org maintainer transition; romainmenke has 1138 approved packages and 0 rejections — not a suspicious takeover.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is a well-established csstools maintainer; this addition reflects a legitimate org-level maintainer transition, not a compromise.	ai	2026/04/24
phantom-deps	phantom-dep:@csstools/css-color-parser	AI (phantom-deps): Same-org @csstools/* dep; indirect usage is expected in the csstools postcss-plugins monorepo ecosystem.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-parser-algorithms	AI (phantom-deps): Same-org @csstools/* dep; indirect usage is expected in the csstools postcss-plugins monorepo ecosystem.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/utilities	AI (phantom-deps): Same-org @csstools/* dep used indirectly via monorepo; not a direct import but a legitimate transitive dependency pattern for this package family.	ai	2026/04/21
license	uncommon-license:MIT-0	AI (license): MIT-0 is a well-known permissive license (MIT without attribution) used consistently across the entire csstools ecosystem. Not a security concern.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/postcss-progressive-custom-properties	AI (phantom-deps): Same-org @csstools/* dep; indirect usage is expected in the csstools postcss-plugins monorepo ecosystem.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-tokenizer	AI (phantom-deps): Same-org @csstools/* dep; indirect usage is expected in the csstools postcss-plugins monorepo ecosystem.	ai	2026/04/21

Versions (showing 50 of 50)

Version	Deps	Published
5.0.4	5 / 0	2026-05-13
5.0.3	5 / 0	2026-04-12
5.0.2	5 / 0	2026-02-21
5.0.1	5 / 0	2026-01-25
5.0.0	5 / 0	2026-01-14
4.0.12	5 / 0	2025-09-21
4.0.11	5 / 0	2025-08-22
4.0.10	5 / 0	2025-05-27
4.0.9	5 / 0	2025-04-19
4.0.8	5 / 0	2025-02-23
4.0.7	5 / 0	2024-12-27
4.0.6	5 / 0	2024-11-11
4.0.5	5 / 0	2024-11-01
4.0.4	5 / 0	2024-10-23
4.0.3	5 / 0	2024-10-10
4.0.2	5 / 0	2024-08-18
4.0.1	5 / 0	2024-08-14
4.0.0	5 / 0	2024-08-03
3.0.19	5 / 0	2024-07-07
3.0.18	5 / 0	2024-07-06
3.0.17	5 / 0	2024-06-29
3.0.16	5 / 0	2024-05-04
3.0.15	5 / 0	2024-05-04
3.0.14	5 / 0	2024-04-21
3.0.13	5 / 0	2024-03-31
3.0.12	5 / 0	2024-03-17
3.0.11	5 / 0	2024-03-13
3.0.10	5 / 0	2024-02-19
3.0.9	4 / 0	2023-12-31
3.0.8	4 / 0	2023-12-15
3.0.7	4 / 1	2023-10-09
3.0.6	4 / 1	2023-10-02
3.0.5	4 / 1	2023-09-24
3.0.4	4 / 1	2023-09-18
3.0.3	4 / 1	2023-09-02
3.0.2	4 / 1	2023-08-28
3.0.1	4 / 1	2023-07-24
3.0.0	4 / 1	2023-07-03
2.2.3	4 / 1	2023-06-01
2.2.2	4 / 1	2023-05-19
2.2.1	4 / 1	2023-04-10
2.2.0	4 / 1	2023-03-25
2.1.0	3 / 0	2023-02-06
2.0.1	2 / 0	2023-01-28
2.0.0	2 / 0	2023-01-24
1.1.1	2 / 0	2022-07-08
1.1.0	2 / 0	2022-04-04
1.0.2	2 / 0	2022-03-08
1.0.1	2 / 0	2022-02-12
1.0.0	2 / 0	2022-02-11

v5.0.4

1 finding

LOW No provenance attestation provenance

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

v5.0.2

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.

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

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

v4.0.12

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.

v4.0.11

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.

v4.0.10

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.

v4.0.9

1 finding

LOW No provenance attestation provenance

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

v4.0.8

1 finding

LOW No provenance attestation provenance

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

v4.0.7

1 finding

LOW No provenance attestation provenance

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

v4.0.6

1 finding

LOW No provenance attestation provenance

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

v4.0.5

1 finding

LOW No provenance attestation provenance

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

v4.0.4

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

1 finding

LOW No provenance attestation provenance

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

v3.0.18

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

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

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

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

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

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

2 findings

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

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

2 findings

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

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

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2024-02-19) provenance

This version was published by a different npm account than previous versions on 2024-02-19. 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.9

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-12-31) provenance

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

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

2 findings

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

This version was published by a different npm account than previous versions on 2023-10-09. 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.6

2 findings

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

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

2 findings

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

This version was published by a different npm account than previous versions on 2023-09-24. 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-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.3

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

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

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-07-24) provenance

This version was published by a different npm account than previous versions on 2023-07-24. 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.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.1.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.1

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.