@csstools/postcss-font-format-keywords
Use unquoted format on @font-face CSS definitions.
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 documented csstools org maintainer with 1010 approved packages and 0 rejections; this is a legitimate maintainer transition within the csstools ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): romainmenke is a well-established, trusted publisher in the csstools org; addition is a legitimate transition, not a takeover. | ai | |
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is a recognized permissive license (MIT without attribution) used consistently across the csstools ecosystem. Not a security or legal risk. | ai | |
| phantom-deps | phantom-dep:@csstools/utilities | AI (phantom-deps): Same-org dependency within the csstools monorepo; phantom detection is a false positive for monorepo build patterns. | ai | |
| phantom-deps | phantom-dep:postcss-value-parser | AI (phantom-deps): Referenced in config files as documented; phantom detection is a false positive for this build setup. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.0.2 | 2 / 0 | |
| 3.0.1 | 1 / 0 | |
| 3.0.0 | 1 / 1 | |
| 2.0.2 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 |
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
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.
v3.0.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.
v3.0.0
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. Consider requesting the maintainer enable provenance via CI/CD.
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.