← Home

string-strip-html

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

royston

Keywords

codeextractfromhtmljspmixedremoveseparatestristringstriptagstemplatingtextxhtml

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:lodash-es AI (phantom-deps): Bundled ESM package via esbuild/rollup; lodash-es is a declared runtime dep resolved at build time, not via direct import statements. False positive for this build pattern. ai
phantom-deps phantom-dep:codsen-utils AI (phantom-deps): codsen-utils is a legitimate codsen monorepo dependency resolved via bundler config, not direct import. Consistent false positive for this build setup. ai
phantom-deps phantom-dep:ranges-apply AI (phantom-deps): ranges-apply is a legitimate codsen monorepo dependency resolved via bundler config. False positive for this ESM bundle build pattern. ai
phantom-deps phantom-dep:html-entities AI (phantom-deps): html-entities is a declared runtime dep in a bundled ESM package; phantom-dep false positive for esbuild/rollup build pattern. ai
phantom-deps phantom-dep:string-left-right AI (phantom-deps): string-left-right is a legitimate codsen monorepo dependency resolved via bundler. False positive for this build pattern. ai
phantom-deps phantom-dep:@types/lodash-es AI (phantom-deps): Type-only package; phantom-dep finding is expected and benign for TypeScript-typed packages. ai

Versions (showing 3 of 3)

Version Deps Published
13.5.3 7 / 3
13.4.23 7 / 3
13.4.13 7 / 3

v13.5.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v13.4.23

2 findings
HIGH Publisher changed: royston → GitHub Actions (on 2025-10-08) provenance

This version was published by a different npm account than previous versions on 2025-10-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v13.4.13

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.