domutils
Utilities for working with htmlparser2's dom
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): feedic and fb55 are the same person (Felix Boehm); feedic.com is his email domain, fb55 is his GitHub. Not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): fb55 is the original author Felix Boehm; feedic was his prior npm username. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): feedic is Felix Boehm's old npm account; removal is account consolidation, not a takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Publishing moved to GitHub Actions CI/CD with SLSA provenance; this is a security improvement. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Gap is between vetted v2.8.0 and v4.0.1; intermediate v3.x versions were published. Not truly dormant. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.0.2 | 3 / 11 | |
| 4.0.1 | 3 / 11 | |
| 4.0.0 | 3 / 11 | |
| 3.2.2 | 3 / 13 | |
| 3.2.1 | 3 / 13 | |
| 3.2.0 | 3 / 13 | |
| 3.1.0 | 3 / 13 | |
| 3.0.1 | 3 / 13 | |
| 3.0.0 | 3 / 13 | |
| 2.8.0 | 3 / 13 |
v4.0.1
3 findingsAll previous maintainers (feedic) were replaced by new maintainers (fb55). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
3 findingsAll previous maintainers (feedic) were replaced by new maintainers (fb55). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage 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.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.