Fixes land on the latest published minor of prismatic. Older
minors are not patched — upgrade to the newest release on
pub.dev before reporting.
| Version | Supported |
|---|---|
| Latest minor | Yes |
| Anything older | No — upgrade first |
Do not open a public issue for a security report.
Use GitHub's private vulnerability reporting: go to the Security tab of the repository and press Report a vulnerability. That opens a private advisory visible only to you and the maintainers.
If you cannot use that form, email support@simplify.jobs instead.
Helpful things to include: the package version, the Flutter version and platform, a minimal reproduction, and what an attacker gains.
- Acknowledgement within 5 business days.
- An assessment — whether it is in scope, and the severity we assign it — once we have reproduced it.
- A fix released on the latest minor, and a GitHub Security Advisory published when the issue warrants one. We are happy to credit you unless you would rather stay anonymous.
Please give us a reasonable window to ship a fix before disclosing publicly.
This is a rendering package. It draws two effects with fragment shaders
that ship inside the package — BorderBeam, animated light around a
widget's border (shaders/beam.frag), and DistortionWave, a wave that
carries one view into another (shaders/wave.frag and
shaders/wave_glow.frag). It opens no sockets, reads no files other than
its own bundled shader assets, writes nothing, stores nothing, and collects
nothing. Its only runtime dependencies are the Flutter SDK and
material_ui, for the Material theme
the beam reads its surface from.
Most of the vulnerability classes a security report usually covers simply
have no surface here.
In scope:
- Attacker-controllable input to the public API — colors, stops, radii, durations, segment anchors, wave styles, palettes, sources and progress — that causes a crash, an unbounded allocation, a hang, or an unrecoverable render-loop failure in a host app.
- A compromise of the release path: the publishing workflow, the pub.dev
automated-publishing configuration, or the published archive's contents
(including the shaders:
shaders/*.fragand theshaders/common/*.glslthey include). - Anything in the package that reaches the network or the filesystem. There should be nothing; if you find something, that is the report.
Out of scope:
- Visual bugs, jank, and performance that is merely disappointing — those are ordinary issues.
- Frame-rate or battery cost of an animation configured to be expensive.
- Vulnerabilities in Flutter, Dart, or a browser engine — report those to their own projects.
- The example app and its hosted live demo, which contain no data and no accounts.