stylis MIT 51 versions

stylis

npm Repository Homepage

A Light–weight CSS Preprocessor

51

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

andaristthysultan

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/stylis.cjs	AI (source-diff): Minified CJS bundle produced by rollup+terser build pipeline; standard dist output for this CSS preprocessor package.	ai	2026/04/24
source-diff	obfuscated-file:dist/stylis.mjs	AI (source-diff): Minified output from rollup+terser build pipeline; source shipped in src/. Standard for this CSS preprocessor package.	ai	2026/04/24
source-diff	obfuscated-file:dist/umd/stylis.js	AI (source-diff): dist/umd/stylis.js is the Rollup+Terser minified UMD bundle — standard build output for this CSS preprocessor library. Not obfuscation.	ai	2026/04/24
source-diff	obfuscated-file:dist/stylis.js	AI (source-diff): dist/stylis.js is the rollup+terser minified UMD bundle; standard build output for this CSS preprocessor library. Stable across versions.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition to andarist, a highly trusted publisher in the styled-components/emotion ecosystem where stylis is a core dep.	ai	2026/04/23

Versions (showing 51 of 177)

View all versions

Version	Deps	Published
4.4.0	0 / 10	2026-04-19
4.3.6	0 / 10	2025-02-06
4.3.5	0 / 10	2025-01-13
4.3.4	0 / 10	2024-08-22
4.3.3	0 / 10	2024-08-21
4.3.2	0 / 10	2024-04-23
4.3.1	0 / 10	2023-12-27
4.3.0	0 / 10	2023-06-27
4.2.0	0 / 10	2023-05-05
4.1.4	0 / 10	2023-04-28
4.1.3	0 / 10	2022-10-26
4.1.2	0 / 10	2022-09-09
4.1.1	0 / 10	2022-04-23
4.1.0	0 / 10	2022-04-03
4.0.13	0 / 10	2021-12-11
4.0.12	0 / 10	2021-12-10
4.0.11	0 / 10	2021-12-09
4.0.10	0 / 10	2021-04-07
4.0.9	0 / 10	2021-03-25
4.0.8	0 / 10	2021-03-21
4.0.7	0 / 10	2021-01-29
4.0.6	0 / 10	2020-12-02
4.0.5	0 / 10	2020-12-02
4.0.4	0 / 10	2020-12-01
4.0.3	0 / 10	2020-09-14
4.0.2	0 / 10	2020-06-25
4.0.1	0 / 9	2020-05-23
4.0.0	0 / 9	2020-04-23
3.5.4	0 / 1	2018-11-09
3.5.3	0 / 1	2018-07-13
3.5.2	0 / 1	2018-07-12
3.5.1	0 / 1	2018-06-19
3.5.0	0 / 1	2018-03-08
3.4.10	0 / 1	2018-02-17
3.4.9	0 / 1	2018-02-15
3.4.8	0 / 1	2018-01-11
3.4.7	0 / 1	2018-01-08
3.4.6	0 / 1	2018-01-08
3.4.5	0 / 0	2017-11-25
3.4.4	0 / 0	2017-11-22
3.4.3	0 / 0	2017-11-14
3.4.2	0 / 0	2017-11-13
3.4.1	0 / 0	2017-11-11
3.4.0	0 / 0	2017-10-20
3.3.2	0 / 0	2017-10-11
3.3.1	0 / 0	2017-10-09
3.3.0	0 / 0	2017-10-08
3.2.20	0 / 0	2017-10-06
3.2.19	0 / 0	2017-09-28
3.2.18	0 / 0	2017-09-25
3.2.17	0 / 0	2017-09-21

v4.3.5

2 findings

HIGH Publisher changed: thysultan → andarist (on 2025-01-13) provenance

This version was published by a different npm account than previous versions on 2025-01-13. 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.

v4.3.4

2 findings

HIGH Publisher changed: andarist → thysultan (on 2024-08-22) provenance

This version was published by a different npm account than previous versions on 2024-08-22. 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.

v4.3.3

2 findings

HIGH Publisher changed: andarist → thysultan (on 2024-08-21) provenance

This version was published by a different npm account than previous versions on 2024-08-21. 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.

v4.3.2

1 finding

LOW No provenance attestation provenance

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

v4.3.1

1 finding

LOW No provenance attestation provenance

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

v4.3.0

1 finding

LOW No provenance attestation provenance

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

v4.1.4

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: thysultan → andarist (on 2023-04-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-28. This could indicate a legitimate maintainer transition or an account compromise.

v4.1.3

1 finding

LOW No provenance attestation provenance

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

v4.1.2

1 finding

LOW No provenance attestation provenance

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

v4.1.1

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.13

1 finding

LOW No provenance attestation provenance

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

v4.0.12

1 finding

LOW No provenance attestation provenance

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

v4.0.11

1 finding

LOW No provenance attestation provenance

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

v4.0.10

1 finding

LOW No provenance attestation provenance

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

v4.0.9

1 finding

LOW No provenance attestation provenance

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

v4.0.8

1 finding

LOW No provenance attestation provenance

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

v4.0.7

1 finding

LOW No provenance attestation provenance

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

v4.0.6

2 findings

HIGH New obfuscated file: dist/umd/stylis.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v4.0.5

2 findings

HIGH New obfuscated file: dist/umd/stylis.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v4.0.4

2 findings

HIGH New obfuscated file: dist/stylis.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v4.0.3

2 findings

HIGH New obfuscated file: dist/stylis.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v4.0.2

2 findings

HIGH New obfuscated file: dist/stylis.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v4.0.1

1 finding

LOW No provenance attestation provenance

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

v4.0.0

2 findings

HIGH New obfuscated file: dist/stylis.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v3.5.4

1 finding

LOW No provenance attestation provenance

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

v3.5.3

1 finding

LOW No provenance attestation provenance

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

v3.5.2

1 finding

LOW No provenance attestation provenance

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

v3.5.1

1 finding

LOW No provenance attestation provenance

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

v3.5.0

1 finding

LOW No provenance attestation provenance

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

v3.4.10

1 finding

LOW No provenance attestation provenance

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

v3.4.9

1 finding

LOW No provenance attestation provenance

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

v3.4.8

1 finding

LOW No provenance attestation provenance

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

v3.4.7

1 finding

LOW No provenance attestation provenance

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

v3.4.6

1 finding

LOW No provenance attestation provenance

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

v3.4.5

1 finding

LOW No provenance attestation provenance

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

v3.4.4

1 finding

LOW No provenance attestation provenance

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

v3.4.3

1 finding

LOW No provenance attestation provenance

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

v3.4.2

1 finding

LOW No provenance attestation provenance

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

v3.4.1

1 finding

LOW No provenance attestation provenance

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.20

1 finding

LOW No provenance attestation provenance

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

v3.2.19

1 finding

LOW No provenance attestation provenance

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

v3.2.18

1 finding

LOW No provenance attestation provenance

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

v3.2.17

1 finding

LOW No provenance attestation provenance

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