← Home

rework-font-variant

Implements the font-variant-* properties for browsers that don't yet support them.

5
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

ianstormtaylormoox

Keywords

font-variantfontvariantreworktypetypographyopentypefeaturefont-feature-settings

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from ianstormtaylor to moox occurred in 2014 (~10 years ago). moox has 810 approved packages and 0 rejected — a well-established publisher. This is a stable historical transition, not a takeover. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer addition of moox occurred in 2014. moox has a strong track record (810 approved, 0 rejected). Stable historical change, not a current risk. ai
publish-pattern dormant-publish AI (publish-pattern): Dormant publish occurred in 2014 during a legitimate maintainer transition. No ongoing pattern of suspicious dormancy; package has been stable since. ai

Versions (showing 5 of 5)

Version Deps Published
1.0.1 0 / 3
1.0.0 0 / 3
0.0.3 0 / 3
0.0.2 0 / 3
0.0.1 0 / 3

v1.0.1

2 findings
HIGH Publisher changed: ianstormtaylor → moox (on 2014-06-27) provenance

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

1 finding
LOW No provenance attestation provenance

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

v0.0.3

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.