← Home

rework-vars

npm Repository Homepage

CSS spec style variables for Rework

10
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

tjholowaychuknecolas

Keywords

cssreworkrework-pluginvariablesvars

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Historical maintainer transition from tjholowaychuk to necolas in Dec 2013 — both are well-known, reputable npm publishers. Over 11 years old; no risk. ai
provenance no-provenance AI (provenance): Established package from a highly trusted publisher; lack of Sigstore provenance is expected for packages of this age and does not indicate risk. ai

Versions (showing 10 of 10)

Version Deps Published
3.1.1 2 / 2
3.1.0 2 / 2
3.0.0 1 / 3
2.0.3 1 / 3
2.0.2 1 / 3
2.0.1 1 / 3
2.0.0 1 / 3
1.1.0 1 / 3
1.0.1 1 / 0
1.0.0 1 / 0

v3.1.1

1 finding
INFO No provenance attestation provenance

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

v3.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] 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.3

1 finding
INFO No provenance attestation provenance

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

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

2 findings
HIGH Publisher changed: tjholowaychuk → necolas (on 2013-12-18) provenance

This version was published by a different npm account than previous versions on 2013-12-18. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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