← Home

posthtml-match-helper

npm Repository Homepage

A helper to expand CSS selectors into PostHTML matcher objects

6
Versions
MIT
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

cossssminphloe

Keywords

posthtmlposthtml-helperposthtml-matcher

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transfer within the posthtml GitHub org; cossssmin is a known PostHTML maintainer with clean track record. ai
maintainer-change maintainer-added AI (maintainer-change): cossssmin is a known PostHTML org maintainer; transfer is consistent with org-level maintenance handoff. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.3 0 / 3
2.0.2 0 / 3
2.0.1 0 / 5
2.0.0 0 / 5
1.0.1 0 / 0
1.0.0 0 / 0

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

2 findings
HIGH Publisher changed: phloe → cossssmin (on 2024-02-28) provenance

This version was published by a different npm account than previous versions on 2024-02-28. 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.

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.