@csstools/css-tokenizer MIT 23 versions

@csstools/css-tokenizer

npm Repository Homepage

Tokenize CSS

23

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

jonathantnealalagunaromainmenke

Keywords

csstokenizer

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Both alaguna and romainmenke are listed as contributors in package.json; transition is within the csstools org. romainmenke has 945 approved packages and strong track record.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is a co-contributor in package.json and a highly trusted publisher (945 approved/0 rejected). Addition is a legitimate org-level transition.	ai	2026/04/24

Versions (showing 23 of 23)

Version	Deps	Published
4.0.0	0 / 0	2026-01-14
3.0.4	0 / 0	2025-05-27
3.0.3	0 / 0	2024-10-25
3.0.2	0 / 0	2024-10-10
3.0.1	0 / 0	2024-08-18
3.0.0	0 / 0	2024-08-03
2.4.1	0 / 0	2024-07-05
2.4.0	0 / 0	2024-07-05
2.3.3	0 / 0	2024-07-03
2.3.2	0 / 0	2024-06-29
2.3.1	0 / 0	2024-05-04
2.3.0	0 / 0	2024-05-04
2.2.4	0 / 0	2024-03-13
2.2.3	0 / 0	2023-12-31
2.2.2	0 / 0	2023-12-15
2.2.1	0 / 2	2023-09-24
2.2.0	0 / 2	2023-07-24
2.1.1	0 / 2	2023-04-10
2.1.0	0 / 2	2023-02-21
2.0.2	0 / 2	2023-02-13
2.0.1	0 / 2	2023-01-28
2.0.0	0 / 2	2023-01-19
1.0.0	0 / 0	2022-11-14

v3.0.4

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.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.

v2.3.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.

v2.3.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.

v2.2.4

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2024-03-13) provenance

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

v2.2.3

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-12-31) provenance

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

v2.2.2

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-12-15) provenance

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

v2.2.1

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-09-24) provenance

This version was published by a different npm account than previous versions on 2023-09-24. 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.

v2.2.0

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2023-07-24) provenance

This version was published by a different npm account than previous versions on 2023-07-24. 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.

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

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

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

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.