@csstools/postcss-media-minmax
Use the range notation in CSS media queries
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): romainmenke is a listed contributor in package.json and a well-established csstools maintainer (1100 approved packages, 0 rejected). Transition from alaguna is legitimate within the csstools org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): romainmenke is already a contributor in package.json and a trusted csstools org maintainer. This is a legitimate handoff, not a takeover. | ai | |
| phantom-deps | phantom-dep:@csstools/css-calc | AI (phantom-deps): Same-org @csstools scoped dep; declared as runtime dependency and used transitively. Not a real phantom dep risk for this package. | ai | |
| phantom-deps | phantom-dep:@csstools/css-tokenizer | AI (phantom-deps): Same-org @csstools scoped dep; declared as runtime dependency and used transitively. Not a real phantom dep risk for this package. | ai | |
| phantom-deps | phantom-dep:@csstools/css-parser-algorithms | AI (phantom-deps): Same-org @csstools scoped dep; declared as runtime dependency and used transitively. Not a real phantom dep risk for this package. | ai | |
| phantom-deps | phantom-dep:@csstools/media-query-list-parser | AI (phantom-deps): Same-org @csstools scoped dep; declared as runtime dependency and used transitively. Not a real phantom dep risk for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 4 / 0 | |
| 3.0.2 | 4 / 0 | |
| 3.0.1 | 4 / 0 | |
| 3.0.0 | 4 / 0 | |
| 2.0.9 | 4 / 0 | |
| 2.0.8 | 4 / 0 | |
| 2.0.7 | 4 / 0 | |
| 2.0.6 | 4 / 0 | |
| 2.0.5 | 4 / 0 | |
| 2.0.4 | 4 / 0 | |
| 2.0.3 | 4 / 0 | |
| 2.0.2 | 4 / 0 | |
| 2.0.1 | 4 / 0 | |
| 2.0.0 | 4 / 0 | |
| 1.1.8 | 4 / 0 | |
| 1.1.7 | 4 / 0 | |
| 1.1.6 | 4 / 0 | |
| 1.1.5 | 4 / 0 | |
| 1.1.4 | 4 / 0 | |
| 1.1.3 | 4 / 0 | |
| 1.1.2 | 4 / 0 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 4 / 1 | |
| 1.0.7 | 4 / 1 | |
| 1.0.6 | 4 / 1 | |
| 1.0.5 | 4 / 1 | |
| 1.0.4 | 4 / 1 | |
| 1.0.3 | 4 / 1 | |
| 1.0.2 | 4 / 1 | |
| 1.0.1 | 4 / 1 | |
| 1.0.0 | 4 / 1 |
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
2 findingsThis version was published by a different npm account than previous versions on 2023-08-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.