← Home

rework-import

npm Repository Homepage

A rework plugin to read and inline CSS files via @import

13
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

jxsonmooxkevva

Keywords

cssimportmediarework

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from jxson to moox occurred in 2014 as a documented, legitimate maintainer transition; all contributors listed in package.json authors field. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers moox and kevva are explicitly listed as authors in package.json; this is a transparent, collaborative handoff from 2014. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected for 2014-era packages. ai

Versions (showing 13 of 13)

Version Deps Published
2.1.0 4 / 3
2.0.1 4 / 3
2.0.0 4 / 3
1.2.1 3 / 3
1.2.0 3 / 3
1.1.3 3 / 3
1.1.2 3 / 3
1.1.1 4 / 3
1.1.0 4 / 3
1.0.0 4 / 2
0.0.3 2 / 0
0.0.2 2 / 0
0.0.1 2 / 0

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

2 findings
HIGH Publisher changed: moox → kevva (on 2014-09-05) provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.1.2

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

2 findings
HIGH Publisher changed: jxson → 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.

v1.0.0

2 findings
HIGH Publisher changed: jxson → moox (on 2014-06-14) provenance

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