← Home

@csstools/postcss-unset-value

npm Repository Homepage

Use the unset keyword in CSS.

9
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

inheritinitialpostcss-pluginunset

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): romainmenke is a well-established csstools maintainer (1215 approved packages, 0 rejected); both original author and new publisher are listed as contributors in package.json, confirming a legitimate handoff. ai
maintainer-change maintainer-added AI (maintainer-change): romainmenke is a known csstools ecosystem maintainer with a strong track record; addition reflects legitimate org-level maintainer transition. ai
license uncommon-license:MIT-0 AI (license): MIT-0 is a recognized OSI-approved license used consistently across csstools packages; no legal risk. ai

Versions (showing 9 of 9)

Version Deps Published
5.0.0 0 / 0
4.0.0 0 / 0
3.0.1 0 / 0
3.0.0 0 / 1
2.0.1 0 / 0
2.0.0 0 / 0
1.0.2 0 / 0
1.0.1 0 / 0
1.0.0 0 / 0

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

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.

v3.0.0

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

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

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.