video-react
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/video-react.full.min.js | AI (source-diff): Minified UMD bundle output, not a dropper; pattern is standard require/exports wrapper. | ai | |
| source-diff | net-exec-file:dist/video-react.full.js | AI (source-diff): Rollup UMD bundle boilerplate, not real network+exec malware. | ai | |
| phantom-deps | phantom-dep:lodash.throttle | AI (phantom-deps): Used inside bundled dist output; not scannable via source import grep. | ai | |
| source-diff | net-exec-file-transition:dist/video-react.js | AI (source-diff): Fires on webpack UMD bundle: core-js Function('return this') + URL-shaped comments. No real network/eval. Stable FP for this dist file. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 5 / 62 | |
| 0.11.2 | 4 / 57 | |
| 0.11.1 | 4 / 57 | |
| 0.11.0 | 4 / 57 | |
| 0.10.5 | 4 / 57 | |
| 0.10.4 | 2 / 24 | |
| 0.10.3 | 2 / 24 | |
| 0.10.1 | 2 / 23 | |
| 0.9.2 | 2 / 20 | |
| 0.9.1 | 2 / 20 | |
| 0.9.0 | 2 / 20 | |
| 0.8.9 | 3 / 52 | |
| 0.8.2 | 3 / 52 | |
| 0.7.8 | 2 / 50 | |
| 0.7.7 | 2 / 50 | |
| 0.7.5 | 2 / 50 | |
| 0.7.3 | 2 / 50 | |
| 0.7.2 | 2 / 50 | |
| 0.7.1 | 2 / 50 | |
| 0.7.0 | 2 / 50 | |
| 0.6.4 | 2 / 50 | |
| 0.6.3 | 2 / 50 | |
| 0.6.2 | 2 / 50 | |
| 0.6.1 | 2 / 50 | |
| 0.5.1 | 2 / 49 | |
| 0.4.4 | 2 / 49 | |
| 0.4.3 | 2 / 49 | |
| 0.4.2 | 2 / 48 | |
| 0.4.1 | 3 / 47 | |
| 0.3.3 | 2 / 47 | |
| 0.3.2 | 2 / 47 | |
| 0.3.1 | 2 / 47 | |
| 0.2.4 | 2 / 47 | |
| 0.2.3 | 2 / 47 | |
| 0.2.2 | 3 / 47 | |
| 0.2.1 | 3 / 47 | |
| 0.1.4 | 3 / 46 | |
| 0.1.3 | 3 / 46 | |
| 0.1.2 | 3 / 46 | |
| 0.1.1 | 3 / 46 | |
| 0.0.2 | 2 / 45 | |
| 0.0.1 | 0 / 39 |
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
2 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
2 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.