@csstools/postcss-nested-calc MIT-0 9 versions

@csstools/postcss-nested-calc

npm Repository Homepage

Use nested calc() expressions in CSS

9

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

calccssmathnestedpostcss-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): romainmenke is a well-established csstools org contributor listed as a co-contributor in package.json; transition from alaguna is a documented, legitimate handoff within the csstools ecosystem.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is a known csstools org maintainer with 1117 approved packages and 0 rejections; addition is a legitimate org-level maintainer transition.	ai	2026/04/24
phantom-deps	phantom-dep:@csstools/utilities	AI (phantom-deps): Same-org dependency from csstools monorepo; used in compiled dist output. Stable false positive for this package.	ai	2026/04/21
phantom-deps	phantom-dep:postcss-value-parser	AI (phantom-deps): Well-known CSS parsing utility; referenced in config/build files. Not a risk for this package.	ai	2026/04/21
license	uncommon-license:MIT-0	AI (license): MIT-0 is a recognized permissive license used consistently across the csstools organization. No legal risk.	ai	2026/04/21

Versions (showing 9 of 9)

Version	Deps	Published
5.0.0	2 / 0	2026-01-14
4.0.0	2 / 0	2024-08-03
3.0.2	2 / 0	2024-02-19
3.0.1	1 / 0	2023-12-15
3.0.0	1 / 1	2023-07-03
2.0.2	1 / 0	2023-02-09
2.0.1	1 / 0	2023-01-28
2.0.0	1 / 0	2023-01-24
1.0.0	1 / 0	2022-08-15

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

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

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