posthtml-parser — Greenflagged

Parse HTML/XML to PostHTMLTree

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

voischevmrmlncscrum

Keywords

htmlxmlparserposthtmlposthtmltree

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within the posthtml org; mrmlnc is a long-standing trusted publisher (3403 days, 58 approvals).	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): mrmlnc added as maintainer in 2017 as part of normal posthtml org maintenance; well-established publisher.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package published in 2017, before Sigstore provenance existed; expected for this era.	ai	2026/04/24
source-diff	obfuscated-file:coverage/lcov-report/prettify.js	AI (source-diff): Istanbul coverage report artifact (Google code-prettify); standard minified library for HTML coverage reports, not malicious.	ai	2026/04/24
source-diff	obfuscated-file:coverage/prettify.js	AI (source-diff): Duplicate Istanbul coverage report prettify.js; standard code-prettify library, not obfuscated payload.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase from accidentally published coverage/ directory; no malicious payload.	ai	2026/04/24

Versions (showing 35 of 35)

Version	Deps	Published
0.12.1	1 / 12	2024-09-19
0.12.0	1 / 12	2023-10-25
0.11.0	1 / 19	2022-02-25
0.10.2	1 / 19	2022-01-17
0.10.1	1 / 19	2021-08-30
0.10.0	1 / 19	2021-07-28
0.9.1	1 / 19	2021-07-26
0.9.0	1 / 19	2021-05-11
0.8.5	1 / 19	2021-05-06
0.8.4	1 / 19	2021-05-06
0.8.3	1 / 19	2021-05-06
0.8.2	1 / 19	2021-05-06
0.8.1	1 / 19	2021-05-05
0.8.0	1 / 19	2021-04-16
0.7.2	1 / 19	2021-04-12
0.7.1	1 / 19	2021-02-15
0.7.0	1 / 19	2021-02-09
0.6.0	1 / 13	2020-11-13
0.5.3	1 / 13	2020-11-13
0.5.2	1 / 13	2020-10-30
0.5.1	1 / 13	2020-10-27
0.5.0	1 / 15	2020-08-22
0.4.2	1 / 8	2019-11-08
0.4.1	2 / 8	2018-02-16
0.4.0	3 / 8	2018-01-23
0.3.3	3 / 8	2018-01-19
0.3.2	3 / 8	2018-01-18
0.3.1	3 / 8	2017-12-27
0.3.0	2 / 8	2017-11-22
0.2.1	2 / 8	2017-02-14
0.2.0	2 / 8	2016-07-19
0.1.3	1 / 5	2016-03-04
0.1.2	1 / 5	2016-03-03
0.1.1	1 / 5	2015-11-02
0.1.0	1 / 5	2015-10-20

v0.12.1

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

INFO No provenance attestation provenance

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

v0.11.0

1 finding

INFO No provenance attestation provenance

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

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

INFO No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

INFO No provenance attestation provenance

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

v0.8.5

1 finding

LOW No provenance attestation provenance

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

v0.8.4

1 finding

INFO No provenance attestation provenance

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

v0.8.3

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

INFO No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

INFO No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

3 findings

HIGH New obfuscated file: coverage/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: coverage/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.4.2

3 findings

HIGH New obfuscated file: coverage/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: coverage/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.4.1

1 finding

INFO No provenance attestation provenance

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

v0.4.0

1 finding

INFO No provenance attestation provenance

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

v0.3.3

1 finding

INFO No provenance attestation provenance

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

v0.3.2

1 finding

INFO No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: mrmlnc → scrum (on 2017-11-22) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-11-22. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.1

2 findings

HIGH Publisher changed: voischev → mrmlnc (on 2017-02-14) provenance

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

v0.2.0

1 finding

INFO No provenance attestation provenance

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

v0.1.3

1 finding

INFO No provenance attestation provenance

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

v0.1.2

1 finding

INFO No provenance attestation provenance

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

v0.1.1

1 finding

INFO No provenance attestation provenance

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

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