@csstools/postcss-progressive-custom-properties
Correctly declare progressive enhancements for CSS Custom Properties.
26
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
jonathantnealalagunaromainmenke
Keywords
csscustomdeclarationspostcsspostcss-pluginprogressivepropertiesutilityvariablesvars
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 well-established csstools ecosystem maintainer (1154 approved packages, 0 rejected). The transition from alaguna to romainmenke is a documented legitimate org handoff within csstools. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): romainmenke is a trusted publisher in the csstools org with a strong track record. This maintainer addition is a legitimate transition, not a takeover. | ai | |
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is a well-known permissive license (no-attribution MIT). Stable choice for this package across versions. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 1 / 0 | |
| 5.1.0 | 1 / 0 | |
| 5.0.0 | 1 / 0 | |
| 4.2.1 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.1 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.3.0 | 1 / 0 | |
| 3.2.0 | 1 / 0 | |
| 3.1.1 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 3.0.3 | 1 / 0 | |
| 3.0.2 | 1 / 1 | |
| 3.0.1 | 1 / 1 | |
| 3.0.0 | 1 / 1 | |
| 2.3.0 | 1 / 1 | |
| 2.2.0 | 1 / 1 | |
| 2.1.1 | 1 / 1 | |
| 2.1.0 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.3.0 | 1 / 0 | |
| 1.2.0 | 1 / 0 | |
| 1.1.0 | 1 / 0 | |
| 1.0.0 | 0 / 0 |
v5.1.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.