← Home

rework-calc

calc() support for Rework

4
Versions
MIT
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

joakimbengjonathanongjongleberrylydellnecolasconradzmoox

Keywords

cssreworkrework-pluginscalculationcalc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change occurred in 2014 (10+ years ago) as part of a legitimate transfer to the reworkcss org. moox has 824 approved packages and 0 rejected — no ongoing risk. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainers added in 2014 are well-known reworkcss ecosystem contributors. Historical, legitimate org transfer — not a risk signal. ai
semgrep semgrep:eval-usage AI (semgrep): eval() is used to evaluate parsed CSS calc() math expressions — the core function of this package. Input is constrained to numeric CSS expressions, not arbitrary user input. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years (published 2014). No provenance is expected and not a risk signal for this package. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.0 2 / 3
1.0.0 2 / 2
0.2.2 0 / 3
0.2.1 0 / 3

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

2 findings
HIGH Publisher changed: joakimbeng → moox (on 2014-06-25) provenance

This version was published by a different npm account than previous versions on 2014-06-25. 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.

v0.2.2

1 finding
INFO No provenance attestation provenance

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

v0.2.1

1 finding
INFO No provenance attestation provenance

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