← Home

uncss

npm Repository Homepage

Remove unused CSS styles

20
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

giakkimikelambert

Keywords

optimizeoptimiseunusedrulesselectorCSSHTML

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): uncss uses child_process.execFile to spawn phantomjs for CSS analysis — this is the core documented mechanism of the tool, not malicious. ai
dependencies unvetted-dep:phantomjs AI (dependencies): phantomjs is a core dependency of uncss; it uses PhantomJS to render HTML and analyze CSS usage. Expected and documented. ai
dependencies unvetted-dep:request AI (dependencies): request is used by uncss to fetch remote HTML pages for CSS analysis. Expected dependency for this tool's functionality. ai
semgrep semgrep:dynamic-require AI (semgrep): The dynamic require is an intentional user-facing inject hook (options.inject) documented in uncss's API. It loads user-supplied scripts into jsdom; not an arbitrary code execution risk from the package itself. ai
phantom-deps phantom-dep:commander AI (phantom-deps): commander is a legitimate CLI dependency used in bin/uncss; the phantom-dep flag is a false positive for CLI-only usage patterns. ai

Versions (showing 20 of 20)

Version Deps Published
0.7.7 7 / 8
0.7.6 7 / 9
0.5.5 5 / 0
0.5.4 5 / 0
0.5.3 4 / 0
0.5.2 4 / 0
0.5.1 4 / 0
0.5.0 4 / 0
0.4.4 5 / 0
0.4.3 4 / 0
0.2.6 3 / 0
0.2.5 5 / 0
0.2.4 6 / 0
0.2.3 6 / 0
0.2.2 6 / 0
0.2.1 6 / 0
0.2.0 6 / 0
0.1.2 6 / 0
0.1.1 6 / 0
0.1.0 6 / 0

v0.7.7

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: giakki.

LOW No provenance attestation provenance

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

v0.7.6

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: giakki.

LOW No provenance attestation provenance

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

v0.5.5

1 finding
LOW No provenance attestation provenance

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

v0.5.4

1 finding
LOW No provenance attestation provenance

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

v0.5.3

1 finding
LOW No provenance attestation provenance

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

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.4

1 finding
LOW No provenance attestation provenance

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

v0.4.3

1 finding
LOW No provenance attestation provenance

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

v0.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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