@csstools/postcss-stepped-value-functions MIT-0 31 versions

@csstools/postcss-stepped-value-functions

npm Repository Homepage

Use round, rem and mod functions in CSS

31

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

cssmoduluspostcss-pluginremainderroundstepped

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Both alaguna and romainmenke are listed as contributors in package.json; this is a documented internal handoff within the csstools org, not a hostile takeover.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is a co-contributor in the csstools monorepo with 1188 approved packages and 0 rejected; addition is a legitimate org-internal transition.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): All three new deps (@csstools/css-calc, @csstools/css-tokenizer, @csstools/css-parser-algorithms) are first-party csstools packages from the same monorepo; no third-party risk.	ai	2026/04/24
license	uncommon-license:MIT-0	AI (license): MIT-0 is a well-known permissive license (MIT without attribution clause); stable choice for this package.	ai	2026/04/24
phantom-deps	phantom-dep:@csstools/css-tokenizer	AI (phantom-deps): Dependency is declared in package.json; phantom-dep rule is a false positive for same-org monorepo dependencies.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-parser-algorithms	AI (phantom-deps): Dependency is declared in package.json; phantom-dep rule is a false positive for same-org monorepo dependencies.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-calc	AI (phantom-deps): Dependency is declared in package.json; phantom-dep rule is a false positive for same-org monorepo dependencies.	ai	2026/04/21

Versions (showing 31 of 31)

Version	Deps	Published
5.0.3	3 / 0	2026-05-13
5.0.2	3 / 0	2026-04-12
5.0.1	3 / 0	2026-02-21
5.0.0	3 / 0	2026-01-14
4.0.9	3 / 0	2025-05-27
4.0.8	3 / 0	2025-04-19
4.0.7	3 / 0	2025-02-23
4.0.6	3 / 0	2024-12-27
4.0.5	3 / 0	2024-11-11
4.0.4	3 / 0	2024-11-01
4.0.3	3 / 0	2024-10-23
4.0.2	3 / 0	2024-10-10
4.0.1	3 / 0	2024-08-18
4.0.0	3 / 0	2024-08-03
3.0.10	3 / 0	2024-07-06
3.0.9	3 / 0	2024-06-29
3.0.8	3 / 0	2024-05-04
3.0.7	3 / 0	2024-05-04
3.0.6	3 / 0	2024-03-13
3.0.5	3 / 0	2024-02-19
3.0.4	3 / 0	2023-12-31
3.0.3	3 / 0	2023-12-15
3.0.2	3 / 1	2023-09-24
3.0.1	3 / 1	2023-07-24
3.0.0	3 / 1	2023-07-03
2.1.1	3 / 1	2023-04-10
2.1.0	3 / 0	2023-02-21
2.0.1	1 / 0	2023-01-28
2.0.0	1 / 0	2023-01-24
1.0.1	1 / 0	2022-07-08
1.0.0	1 / 0	2022-05-02

v5.0.3

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

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

1 finding

LOW No provenance attestation provenance

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

v3.0.9

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

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

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

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

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

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

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

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.