csso
CSS minifier with structural optimisations
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/csso.js | AI (source-diff): dist/csso.js is a Rollup UMD bundle of the CSS minifier built via 'npm run build'. The UMD wrapper pattern triggers the rule but contains no actual network calls or malicious code execution. | ai | |
| source-diff | net-exec-file:dist/csso.min.js | AI (source-diff): dist/csso.min.js is the terser-minified version of the Rollup UMD bundle. Same false positive as csso.js — standard browser bundle, not malware. | ai | |
| source-diff | net-exec-file:dist/csso.esm.js | AI (source-diff): dist/csso.esm.js is a legitimate esbuild/rollup bundle of csso+source-map. URL parsing regex and bundler module patterns trigger the rule; no actual network calls or dynamic code execution present. | ai | |
| source-diff | large-new-source-files | AI (source-diff): csso v5 added ESM/CJS dual-module output; large number of new dist/cjs files is expected from the build system refactor. | ai | |
| provenance | no-provenance | AI (provenance): Established package with strong publisher track record; lack of Sigstore provenance is not a security concern here. | ai |
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 5.0.5 | 1 / 6 | |
| 5.0.4 | 1 / 6 | |
| 5.0.3 | 1 / 6 | |
| 5.0.2 | 1 / 6 | |
| 5.0.1 | 1 / 6 | |
| 5.0.0 | 1 / 7 | |
| 4.2.0 | 1 / 10 | |
| 4.1.1 | 1 / 10 | |
| 4.1.0 | 1 / 10 | |
| 4.0.3 | 1 / 10 | |
| 4.0.2 | 1 / 10 | |
| 4.0.1 | 1 / 10 | |
| 4.0.0 | 1 / 10 | |
| 3.5.1 | 1 / 9 | |
| 3.5.0 | 1 / 9 | |
| 3.4.0 | 1 / 9 | |
| 3.3.1 | 1 / 9 | |
| 3.3.0 | 1 / 9 | |
| 3.2.0 | 1 / 9 | |
| 3.1.1 | 1 / 9 | |
| 3.1.0 | 1 / 9 | |
| 3.0.1 | 1 / 8 | |
| 3.0.0 | 1 / 8 | |
| 2.3.2 | 2 / 7 | |
| 2.3.1 | 2 / 7 | |
| 2.3.0 | 2 / 7 | |
| 2.2.1 | 2 / 7 | |
| 2.2.0 | 2 / 7 | |
| 2.1.1 | 2 / 7 | |
| 2.1.0 | 2 / 7 | |
| 2.0.0 | 2 / 7 | |
| 1.8.2 | 2 / 7 | |
| 1.8.1 | 2 / 7 | |
| 1.8.0 | 2 / 7 | |
| 1.7.1 | 2 / 7 | |
| 1.7.0 | 2 / 7 | |
| 1.6.4 | 2 / 7 | |
| 1.6.3 | 2 / 7 | |
| 1.6.2 | 2 / 7 | |
| 1.6.1 | 2 / 7 | |
| 1.6.0 | 2 / 7 | |
| 1.5.4 | 1 / 4 | |
| 1.5.3 | 1 / 4 | |
| 1.5.2 | 1 / 4 | |
| 1.5.1 | 1 / 4 | |
| 1.5.0 | 1 / 4 | |
| 1.4.4 | 1 / 4 | |
| 1.4.3 | 1 / 4 | |
| 1.4.2 | 1 / 4 | |
| 1.4.1 | 1 / 4 | |
| 1.4.0 | 1 / 4 |
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.