@csstools/cascade-layer-name-parser MIT 21 versions

@csstools/cascade-layer-name-parser

npm Repository Homepage

Parse CSS Cascade Layer names.

21

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

cascade-layercssparser

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from alaguna to romainmenke is a documented, legitimate transition within the csstools org. Both are listed as contributors; romainmenke is the primary monorepo maintainer.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): romainmenke is a well-established csstools maintainer (909 approved packages, 0 rejected). Addition reflects legitimate org-level maintainer transition.	ai	2026/04/24

Versions (showing 21 of 21)

Version	Deps	Published
3.0.0	0 / 0	2026-01-14
2.0.5	0 / 0	2025-05-27
2.0.4	0 / 0	2024-11-01
2.0.3	0 / 0	2024-10-23
2.0.2	0 / 0	2024-10-10
2.0.1	0 / 0	2024-08-18
2.0.0	0 / 0	2024-08-03
1.0.13	0 / 0	2024-07-06
1.0.12	0 / 0	2024-06-29
1.0.11	0 / 0	2024-05-04
1.0.10	0 / 0	2024-05-04
1.0.9	0 / 0	2024-03-13
1.0.8	0 / 0	2024-02-19
1.0.7	0 / 0	2023-12-31
1.0.6	0 / 0	2023-12-15
1.0.5	0 / 0	2023-09-24
1.0.4	0 / 0	2023-07-24
1.0.3	0 / 0	2023-07-03
1.0.2	0 / 0	2023-04-10
1.0.1	0 / 0	2023-01-28
1.0.0	0 / 0	2023-01-19

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

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

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.

v1.0.8

2 findings

HIGH Publisher changed: alaguna → romainmenke (on 2024-02-19) provenance

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

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.

v1.0.6

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.

v1.0.5

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.

v1.0.4

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.

v1.0.3

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

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.