MotionPR runs your application and your scenarios in a browser, and reads capture files that may come from CI artifacts of other people's pull requests. Its bugs can become your vulnerabilities. Reports are welcome and are handled first.
Do not open a public issue. Report privately through GitHub:
https://github.com/erenthedeveloper0/motionpr/security/advisories/new
Include what you can of the following; a partial report is still useful:
- the package version (
npx motionpr --version) and the output ofnpx motionpr doctor, - the Node.js version and operating system,
- a minimal reproduction: the capture file, config or page that triggers it,
- what you expected, what happened, and the impact you believe it has.
| Step | Target |
|---|---|
| Acknowledgement of your report | within 3 working days |
| First assessment (confirmed or not, severity) | within 10 working days |
| Fix released | as fast as severity requires; coordinated with you |
| Public advisory | when the fix is available, or at 90 days, whichever comes first |
Every fix is published with a GitHub Security Advisory and a CVE where one applies, and you are credited unless you ask not to be.
MotionPR is an alpha. Until 1.0, only the most recent published prerelease receives
security fixes; upgrade to it before reporting if you can.
| Version | Supported |
|---|---|
latest 0.x prerelease |
✅ |
| anything older | ❌ |
In scope:
- a capture or comparison file that makes MotionPR read or write outside its directory, execute code, or crash in a way that hides a regression (asset ids and paths are validated today);
- a report that executes data from a capture, or loads anything from the network (reports embed data as inert JSON and render all text as text);
- filled values, masked inputs or redacted query parameters reaching captures, reports or logs;
- the generated GitHub Actions workflow granting more than
contents: read, or an unpinned action; - the published package shipping something it should not.
Out of scope: your own motionpr.config.ts and scenarios, which are code you run on purpose;
vulnerabilities in your application that MotionPR merely loads; the browsers themselves
(Chromium, Firefox, WebKit).
- Treat
motionpr.config.tsas code: it is executed. Do not run MotionPR on a config you do not trust with privileges you would not give that code. - The workflow template uses the
pull_requesttrigger, which gives fork pull requests no secrets and a read-only token. Do not switch topull_request_target: see CI security. - MotionPR sends no telemetry and uploads nothing. See Privacy.
The package is published manually by the maintainer from a tagged, CI-tested commit, from a
tarball that was installed and run in a clean project first (pnpm release:prepare). It
carries no npm provenance attestation, because provenance can only be generated by a CI run.
Third-party GitHub Actions in this repository and in the generated workflow are pinned to commit
SHAs and kept current by Dependabot.