@stream-io/video-filters-web
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:mediapipe/wasm/vision_wasm_internal.js | AI (source-diff): Emscripten-compiled MediaPipe WASM loader; minification is expected and matches upstream MediaPipe build artifacts. | ai | |
| source-diff | obfuscated-file:mediapipe/wasm/vision_wasm_nosimd_internal.js | AI (source-diff): Same Emscripten/MediaPipe WASM loader pattern; stable for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Migration from stream-release-bot to GitHub Actions CI; SLSA provenance attestation confirms legitimate CI pipeline. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.5 | 3 / 7 | |
| 0.7.4 | 3 / 7 | |
| 0.4.0 | 2 / 6 | |
| 0.3.0 | 2 / 6 | |
| 0.2.2 | 2 / 6 | |
| 0.2.1 | 1 / 6 | |
| 0.1.7 | 1 / 6 |
v0.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.4
4 findingsThis version was published by a different npm account than previous versions on 2026-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.