@livekit/krisp-noise-filter No license 23 versions

@livekit/krisp-noise-filter

npm

23

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

rdsathedavidzhaofeepslkmatkam_livekitraja-livekitlivekitherzoglukasiopaulwedliulklk_hiroshidc-livekitcnderrauberbenjaminlivekitdanm_livekitduanweiweiocupe_livekitcacheonlysfkatshaypschrisackermannbcherrylkkuba--rektdeckardlk-mikebraunsteinlivekits-hamdananwaranunay_lktom.ezquerromipesicshubhra123yepherthomasyuill-livekitadriancowhamddotoloczoltylk-toubatbrianikristyjoaquin-lkrgauslivekittinalenguyennikita-livekit

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): CI/CD (GitHub Actions) publish under same livekit org; legitimate transition.	ai	2026/07/12
phantom-deps	phantom-dep:@livekit/mutex	AI (phantom-deps): First-party @livekit scope dep; declared-not-imported is a benign heuristic here.	ai	2026/07/12
publish-pattern	new-deps-added	AI (publish-pattern): Added dep is first-party @livekit/mutex.	ai	2026/07/12

Versions (showing 23 of 23)

Version	Deps	Published
0.4.3	2 / 6	2026-04-28
0.4.2	2 / 6	2026-04-27
0.4.1	1 / 6	2026-01-07
0.4.0	1 / 6	2025-12-23
0.2.16	0 / 6	2025-01-23
0.2.15	0 / 6	2025-01-20
0.2.14	0 / 6	2025-01-07
0.2.13	0 / 6	2024-11-15
0.2.12	0 / 6	2024-09-30
0.2.11	0 / 6	2024-09-30
0.2.10	0 / 6	2024-09-30
0.2.9	0 / 6	2024-09-30
0.2.8	0 / 6	2024-09-12
0.2.7	0 / 6	2024-08-29
0.2.6	0 / 6	2024-08-29
0.2.5	0 / 6	2024-07-26
0.2.4	0 / 6	2024-06-12
0.2.2	0 / 6	2024-04-19
0.2.1	0 / 6	2024-03-24
0.2.0	0 / 6	2024-03-20
0.1.6	0 / 6	2024-03-18
0.1.4	0 / 6	2024-03-07
0.1.3	0 / 6	2024-03-06

v0.4.1

2 findings

HIGH Publisher changed: thedavidzhao → GitHub Actions (on 2026-01-07) provenance

This version was published by a different npm account than previous versions on 2026-01-07. 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.4.0

2 findings

HIGH Publisher changed: thedavidzhao → GitHub Actions (on 2025-12-23) provenance

This version was published by a different npm account than previous versions on 2025-12-23. 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.16

1 finding

LOW No provenance attestation provenance

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

v0.2.15

1 finding

LOW No provenance attestation provenance

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

v0.2.14

1 finding

LOW No provenance attestation provenance

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

v0.2.13

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

1 finding

LOW No provenance attestation provenance

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

v0.2.9

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

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.

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: lukasio → thedavidzhao (on 2024-03-20, known maintainer) provenance

This version was published by a different npm account (thedavidzhao) than the most recent previously approved version (lukasio) on 2024-03-20, but thedavidzhao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: lukasio → thedavidzhao (on 2024-03-18, known maintainer) provenance

This version was published by a different npm account (thedavidzhao) than the most recent previously approved version (lukasio) on 2024-03-18, but thedavidzhao is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.1.4

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.

v0.1.3

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.