← Home

css

npm Repository Homepage

CSS parser / stringifier

26
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

anthonyshortclintwoodconradzianstormtaylorjonathanongjongleberrylydellmooxnecolasslexaxtontjholowaychuk

Keywords

cssparserstringifierstylesheet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from tjholowaychuk to jonathanong occurred in Dec 2013 — a well-documented legitimate maintainer transition. jonathanong is a long-standing npm contributor with a strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): jonathanong was added as maintainer in 2013 as part of TJ Holowaychuk's documented package transfers. This is a stable, decade-old transition. ai
provenance no-provenance AI (provenance): Package was published in 2013, years before Sigstore provenance existed. No-provenance is expected and not a risk signal for packages of this era. ai
typosquat typosquat.levenshtein:cors AI (typosquat): 'css' is a legitimate, well-established package name for a CSS parser — not a typosquat of 'cors'. Edit-distance match is coincidental. ai
typosquat typosquat.levenshtein:qs AI (typosquat): 'css' is a legitimate, well-established package name for a CSS parser — not a typosquat of 'qs'. Edit-distance match is coincidental. ai

Versions (showing 26 of 26)

Version Deps Published
2.2.4 4 / 4
2.2.3 4 / 4
2.2.2 4 / 4
2.2.1 4 / 4
2.2.0 4 / 4
2.1.0 4 / 4
2.0.0 3 / 4
1.6.0 2 / 0
1.4.4 2 / 0
1.4.3 2 / 0
1.4.2 2 / 0
1.4.1 2 / 0
1.4.0 2 / 0
1.3.1 2 / 0
1.3.0 2 / 0
1.2.0 2 / 0
1.1.0 2 / 0
1.0.8 2 / 0
1.0.7 2 / 0
1.0.6 2 / 0
1.0.5 2 / 0
1.0.4 2 / 0
1.0.3 2 / 0
1.0.2 2 / 0
1.0.1 2 / 0
1.0.0 2 / 0

v1.6.0

2 findings
HIGH Publisher changed: tjholowaychuk → jonathanong (on 2013-12-23) provenance

This version was published by a different npm account than previous versions on 2013-12-23. 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.4.4

1 finding
LOW No provenance attestation provenance

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

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.1

1 finding
LOW No provenance attestation provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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.

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

v1.0.0

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.