The reviewed findings map to ordinary application behavior: local preview fixtures, controlled CI tests, and a directly invoked builder that fetches pinned React assets into the project’s public output directory. No malicious install-time or import-time behavior, credential theft, or unrelated data transmission was identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The video preview download and filesystem writes occur when a user runs the preview bundle command. CI shell execution occurs in the test helper.
Impact
These operations support preview asset generation and CI testing; no credential collection, unrelated data transmission, or other attack behavior was identified.
Mechanism
The builder fetches pinned React 18 UMD assets from unpkg.com and writes them under the project’s public/videoml directory; the test helper runs a shell using temporary fake tools.
Evidence
public/videoml/vendor/react.production.min.jspublic/videoml/vendor/react-dom.production.min.jspublic/videoml/preview.htmlpublic/videoml/preview-bundle.js