← Home

rework-inherit

npm Repository

Inherit rules from other selectors

13
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

jongleberryconradznecolasanthonyshortianstormtaylormooxclintwoodlydellmichelleslexaxton

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from anthonyshort to michelle occurred in 2014 as part of a legitimate reworkcss org transition; stable historical fact for this package. ai
maintainer-change maintainer-added AI (maintainer-change): Multiple well-known CSS ecosystem maintainers added in 2014 as part of reworkcss org transition; no compromise indicators. ai

Versions (showing 13 of 13)

Version Deps Published
0.2.3 1 / 1
0.2.2 1 / 1
0.2.1 1 / 1
0.2.0 1 / 1
0.1.6 1 / 1
0.1.5 1 / 1
0.1.4 0 / 1
0.1.3 0 / 1
0.1.2 0 / 1
0.1.1 0 / 1
0.1.0 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v0.2.3

2 findings
HIGH Publisher changed: anthonyshort → michelle (on 2014-07-16) provenance

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: jongleberry → anthonyshort (on 2014-05-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-05-08. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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