← Home

@types/htmlparser2

npm
12
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/* packages are type-only and never directly imported in source; phantom-dep findings are expected false positives for all DefinitelyTyped packages. ai
phantom-deps phantom-dep:@types/domutils AI (phantom-deps): @types/* packages are type-only and never directly imported in source; phantom-dep findings are expected false positives for all DefinitelyTyped packages. ai
phantom-deps phantom-dep:@types/domhandler AI (phantom-deps): @types/* packages are type-only and never directly imported in source; phantom-dep findings are expected false positives for all DefinitelyTyped packages. ai
bogus-package bogus-package AI (bogus-package): This is a legitimate stub/deprecated @types package. Tiny payload, no README code, no repo URL, and no keywords are all expected for a stub that intentionally contains no code. ai
phantom-deps phantom-dep:htmlparser2 AI (phantom-deps): htmlparser2 is listed as a dependency intentionally to pull in the real package's bundled types — the entire purpose of this stub package. ai

Versions (showing 12 of 12)

Version Deps Published
4.1.0 1 / 0
3.10.7 4 / 0
3.10.6 4 / 0
3.10.5 3 / 0
3.10.4 3 / 0
3.10.3 3 / 0
3.10.2 3 / 0
3.10.1 3 / 0
3.10.0 3 / 0
3.7.31 1 / 0
3.7.30 0 / 0
3.7.29 0 / 0

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

v3.10.7

1 finding
LOW No provenance attestation provenance

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

v3.10.6

1 finding
LOW No provenance attestation provenance

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

v3.10.5

1 finding
LOW No provenance attestation provenance

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

v3.10.4

1 finding
LOW No provenance attestation provenance

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

v3.10.3

1 finding
LOW No provenance attestation provenance

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

v3.10.2

1 finding
LOW No provenance attestation provenance

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

v3.10.1

1 finding
LOW No provenance attestation provenance

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

v3.10.0

1 finding
LOW No provenance attestation provenance

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

v3.7.31

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

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

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.