← Home

css-parse

npm Repository Homepage

CSS parser

16
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

tjholowaychukjonathanongjongleberryconradznecolasanthonyshortianstormtaylormooxclintwoodlydell

Keywords

cssparserstylesheet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from jonathanong to necolas reflects legitimate reworkcss project maintainer transition; necolas is a highly trusted publisher. ai
maintainer-change maintainer-added AI (maintainer-change): Added maintainers are all well-known members of the reworkcss/component ecosystem; legitimate team expansion. ai
publish-pattern new-deps-added AI (publish-pattern): Dependency on `css` is the intended v2 refactor — css-parse delegates to the parent `css` package from the same reworkcss org. ai

Versions (showing 16 of 16)

Version Deps Published
2.0.0 1 / 0
1.7.0 0 / 4
1.6.0 0 / 4
1.5.3 0 / 2
1.5.2 0 / 2
1.5.1 0 / 2
1.5.0 0 / 2
1.4.0 0 / 2
1.3.0 0 / 2
1.2.0 0 / 2
1.1.0 0 / 2
1.0.4 0 / 2
1.0.3 0 / 2
1.0.2 1 / 2
1.0.1 1 / 2
1.0.0 1 / 2

v2.0.0

2 findings
HIGH Publisher changed: jonathanong → necolas (on 2014-06-18) provenance

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

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: tjholowaychuk → jonathanong (on 2013-12-23) provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.3

1 finding
LOW No provenance attestation provenance

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

v1.5.2

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

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.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.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. Consider requesting the maintainer enable provenance via CI/CD.

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.