@csstools/postcss-relative-color-syntax MIT-0 41 versions

@csstools/postcss-relative-color-syntax

npm Repository Homepage

Use the relative color syntax in CSS

41

Versions

MIT-0

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

colorpostcss-pluginrelative color syntax

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@csstools/utilities	AI (phantom-deps): Same-org @csstools dependency; likely used transitively or bundled. Stable pattern for this monorepo package.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-tokenizer	AI (phantom-deps): Same-org @csstools dependency; consistent with monorepo bundling pattern for this package.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-color-parser	AI (phantom-deps): Same-org @csstools dependency; consistent with monorepo bundling pattern for this package.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/css-parser-algorithms	AI (phantom-deps): Same-org @csstools dependency; consistent with monorepo bundling pattern for this package.	ai	2026/04/21
phantom-deps	phantom-dep:@csstools/postcss-progressive-custom-properties	AI (phantom-deps): Same-org @csstools dependency; consistent with monorepo bundling pattern for this package.	ai	2026/04/21
license	uncommon-license:MIT-0	AI (license): MIT-0 is a well-known permissive license (MIT without attribution). Intentionally used by the csstools project across all their packages.	ai	2026/04/21

Versions (showing 41 of 41)

Version	Deps	Published
4.0.4	5 / 0	2026-05-13
4.0.3	5 / 0	2026-04-12
4.0.2	5 / 0	2026-02-21
4.0.1	5 / 0	2026-01-25
4.0.0	5 / 0	2026-01-14
3.0.12	5 / 0	2025-09-21
3.0.11	5 / 0	2025-08-22
3.0.10	5 / 0	2025-05-27
3.0.9	5 / 0	2025-04-19
3.0.8	5 / 0	2025-02-23
3.0.7	5 / 0	2024-12-27
3.0.6	5 / 0	2024-11-11
3.0.5	5 / 0	2024-11-01
3.0.4	5 / 0	2024-10-23
3.0.3	5 / 0	2024-10-10
3.0.2	5 / 0	2024-08-18
3.0.1	5 / 0	2024-08-14
3.0.0	5 / 0	2024-08-03
2.0.19	5 / 0	2024-07-07
2.0.18	5 / 0	2024-07-06
2.0.17	5 / 0	2024-06-29
2.0.16	5 / 0	2024-05-04
2.0.15	5 / 0	2024-05-04
2.0.14	5 / 0	2024-04-21
2.0.13	5 / 0	2024-03-31
2.0.12	5 / 0	2024-03-17
2.0.11	5 / 0	2024-03-13
2.0.10	5 / 0	2024-02-19
2.0.9	4 / 0	2023-12-31
2.0.8	4 / 0	2023-12-15
2.0.7	4 / 1	2023-10-09
2.0.6	4 / 1	2023-10-02
2.0.5	4 / 1	2023-09-24
2.0.4	4 / 1	2023-09-18
2.0.3	4 / 1	2023-09-02
2.0.2	4 / 1	2023-08-28
2.0.1	4 / 1	2023-07-24
2.0.0	4 / 1	2023-07-03
1.0.2	4 / 1	2023-06-14
1.0.1	4 / 1	2023-06-01
1.0.0	4 / 1	2023-05-19

v4.0.4

1 finding

LOW No provenance attestation provenance

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

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

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

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

v3.0.12

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.

v3.0.11

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.

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

v3.0.9

1 finding

LOW No provenance attestation provenance

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

v3.0.8

1 finding

LOW No provenance attestation provenance

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

v3.0.7

1 finding

LOW No provenance attestation provenance

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

v3.0.6

1 finding

LOW No provenance attestation provenance

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

v3.0.5

1 finding

LOW No provenance attestation provenance

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

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

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

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

v2.0.19

1 finding

LOW No provenance attestation provenance

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

v2.0.18

1 finding

LOW No provenance attestation provenance

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

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

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

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

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